search

MSD-LIVE / issues

0 stars 0 forks source link

Determine how to best sync storyblok changes from dev >> stage >> prod and implement accordingly #192

Open jugovimm opened 4 months ago

jugovimm commented 4 months ago

Three spaces exist in our storyblok account: dev, stage, and prod, with each being used by their respective webapp. Currently, when deploying between dev and stage or stage and prod, we have to manually run the storyblok CLI command to replace everything in the later branch (ie stage) with everything in the earlier branch (ie dev). It would be better if this was an automatic process. Consider whether we should add the CLI command to our deployment scripts in AWS, or whether we shouldn't as this has its own issues (ex. Casey makes changes directly on prod, which are then overwritten later). Is there another solution that would be better, with less headaches down the road?

jugovimm commented 3 months ago

Completed. How we can treat Storyblok in the future:

  1. The dev space is our place for editing anything Storyblok-related as we need
  2. The prod space is Casey's place for editing any content as he sees fit
  3. The stage space is our place for combining our changes with Casey's changes
  4. Add npm run sb-sync:dev-to-stage OR npm run sb-sync:prod-to-stage to AWS stage release script
  5. Add npm run sb-sync:stage-to-prod to AWS prod release script
  6. When releasing changes to stage is complete, we would then manually merge Casey's changes OR our changes into the stage space (depending on whether we want to prioritize dev-to-stage or prod-to-stage scripts above)