Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bring staged changes to mozilla.design to production #25

Open
slightlyoffbeat opened this issue Jun 8, 2022 · 2 comments
Open

Bring staged changes to mozilla.design to production #25

slightlyoffbeat opened this issue Jun 8, 2022 · 2 comments
Assignees

Comments

@slightlyoffbeat
Copy link
Collaborator

The studio team worked with an agency to update mozilla.design.

The changes are on https://mozilladev.wpengine.com/design

We have a multi-blog instance of wordpress. This means all of the blogs share a database. If we push the staged updates live, it will update all of the blogs, and we will likely lose data.

WPengine has stage, dev, and prod. It looks like these updates currently live on dev.

What we will need to do:

  • work with editorial team to pause blog updates for about a day
  • backup all blogs and data (should be automated by wpengine)
  • optional but recommended: duplicate production to the staged instance
  • export the file changes and bring them to staged
  • isolate and export the parts of the database that were updated for mozilla.design from dev and bring them to staged
  • test that everything looks good.
  • push stage to prod
@craigcook
Copy link
Collaborator

We can do a single blog export of just the design blog content from dev and import it to just the design blog on prod, we don't have to do the entire database.

@slightlyoffbeat
Copy link
Collaborator Author

@craigcook that's perfect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants