Update deployment instructions to be more helpful

This commit is contained in:
benjamin melançon 2022-03-11 16:02:54 -05:00
parent 01a4d3d592
commit 328c543e1e

View file

@ -57,7 +57,7 @@ Agaric is currently using a Platform as a Service version of Drutopia with addit
Set up [drutopia_host](https://gitlab.com/drutopia-platform/drutopia_host) and [hosting_private](https://gitlab.com/drutopia-platform/hosting_private), as documented in hosting private.
Then use [ahoy](https://github.com/ahoy-cli/ahoy/), from within the hosting_private directory.
Then use [ahoy](https://github.com/ahoy-cli/ahoy/), from within the hosting_private directory (`cd ~/Projects/drutopia-platform/drutopia_host/hosting_private`).
Ensure all three related repositories are up-to-date with:
@ -77,15 +77,16 @@ To deploy this build to an instance of the site plus config, templates, styles:
ahoy deploy-site agaric_test
```
(And likewise for `agaric_live`.)
(And likewise for `agaric_live`.) Use `deploy-site-force` in place of `deploy-site` if you need to override configuration changes made on live and you are certain you have captured all wanted changes.
Then record the deployment. This applies to both deploy-site and deploy-build record keeping:
Navigate to `/drutopia_host/build_artifacts`
Add all new files generated with `git add . `
Commit the files with a message on what you deployed with `git commit -m "Add artifacts"`
Push the changes to the repo with `git push`
Then record the deployment, logs from both deploy-site and deploy-build:
If you need to overwrite live configuration (only after confirming you've committed any parts you want to keep) you can use ahoy for that too with `deploy-site-force`.
```
cd ~/Projects/drutopia-platform/drutopia_host/build_artifacts
git add .
git commit -m "Add artifacts"
git push
```
### Drupal settings file management