Staged Publishing With Entity Share
summary
Uses Entity Share (JSON:API, Drupal 10/11) to copy nodes, taxonomies, media and paragraphs between separate Drupal instances while excluding config; implements a boolean push to production field to control transfers. Uses cron (every 5 minutes) with a 50-item batch limit, and stage file proxy to avoid duplicating files. Runs as a separate "content stage" site feeding production and 16 country sites, works after retries but needs Cloudflare/Imperva tuning, dependency testing and handling of partial imports.
AI-written summary · about
chapters (9)
- 0:00Introduction to staged publishing
- 2:53How content staging works
- 7:28Shared page dependencies explained
- 11:53Handling media and files
- 15:52Syncing strategies and cron setup
- 24:15When to use entity share
- 27:29Lessons learned and pitfalls
- 31:45Key takeaways and future plans
- 32:50Q&A session
related talks
22mDrupal HA: a story from the trenches
56mHow to keep Drupal relevant in the Git-based and API-driven CMS era
21mThe transformation from Print paper to Digital News & Media with Drupal
16mUsing Drupal as a Content Hub to create an interactive, visual product
15mShipping production web apps on Firebase Hosting
27mMemory of Nations - how Drupal helps to preserve memories of humankind
40mLive preview with Gatsby and decoupled Drupal
53mHopping in the Clouds: migration between cloud providers