Skip to content

Instantly share code, notes, and snippets.

@itsjoekent

itsjoekent/gist:63e4a6afe6f6f659126925b286c3942e

Created October 6, 2017 14:40
Show Gist options
  • Save itsjoekent/63e4a6afe6f6f659126925b286c3942e to your computer and use it in GitHub Desktop.
Save itsjoekent/63e4a6afe6f6f659126925b286c3942e to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.md

sync prod --> staging content

Goal: Have staging mirror production content

tools reference

steps

Run through the following steps every (X) hour

  1. export the production space
  2. wipe the staging space of all entries + content types
  3. import the production space content
  4. make a slack notification?

open questions

  • How does the import/export tooling handle assets? Does this require some additional custom logic?
  • At what point (in terms of export / import size) does this process stop working?
  • How frequently should we sync content? Every hour? Every time we publish content on production?
  • My caution with that level of frequency is interupting developer workflow, but...
  • Should developers just get there own Contentful space? With this tool you could sync up at your own pace and let the staging server stay always up to date.
@DFurnes
Copy link

DFurnes commented Oct 6, 2017

This is pretty darn cool. 👍

@DFurnes
Copy link

DFurnes commented Oct 6, 2017

@itsjoekent Can you turn this into an issue on the phoenix-next repo so it's more discoverable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment