We generally have scripts that automate this but as we are moving towards Oghma handling (or at least be the repository for these scripts in a way) more things like this it could be good for have an outline of what work is being done.
Two kinds of site launches:
Launching a development site (the main site launch we do already, which works well)
Launching a redesigned production site (this needs to be slightly different)
This would include a development site for the redesign work which is then copied over to the already present (now old) production site.
Things to mention in 2. above
we need a manual backup of the old production site BEFORE the new dev site is copied over to the production site
automatic backups are enabled but these are set to be kept for only a month
manual backups are kept (forever??)
manual backups could be used to create a multidev site in the case something is needed from the production site's previous state.
Backups ?
Is there a different way to handle 2. above? Perhaps a database merge or similar. For now a simple database backup should be good but do we want to think about how to incorporate old data in a new site when needed for the future? We are already working on migrating d7 express to d9+ express... Perhaps something similar can be done for situation 2. above?
Outline process for launching sites on Pantheon
We generally have scripts that automate this but as we are moving towards Oghma handling (or at least be the repository for these scripts in a way) more things like this it could be good for have an outline of what work is being done.
Two kinds of site launches:
Things to mention in 2. above
Backups ?
Is there a different way to handle 2. above? Perhaps a database merge or similar. For now a simple database backup should be good but do we want to think about how to incorporate old data in a new site when needed for the future? We are already working on migrating d7 express to d9+ express... Perhaps something similar can be done for situation 2. above?