Skip to content

Commit

Permalink
fix(single-tenant): application upgrades do not need --profile databa…
Browse files Browse the repository at this point in the history
…ses (#9593)
  • Loading branch information
rafaelromcar-parabol authored Apr 2, 2024
1 parent dbc9f09 commit 9486587
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docker/stacks/single-tenant-host/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ To run Parabol in single tenant mode (e.g. simple docker-compose on a docker hos

1. Edit the `docker-compose.yaml` and change the `#image:tag` changing the tag. Ex: from `v7.15.0` to `v7.15.2`.
2. (optional) In a different terminal, run `docker compose logs -f` to follow the upgrade.
3. Run `docker compose --profile databases --profile parabol up -d`. It will start the `pre-deploy` and, once it is done successfully, then it will stop and recreate the `web-server` and `gql-executor` with the new version of the image. **This step implies a downtime**.
3. Run `docker compose --profile parabol up -d`. It will start the `pre-deploy` and, once it is done successfully, then it will stop and recreate the `web-server` and `gql-executor` with the new version of the image. **This step implies a downtime**.
4. Verify the application is still up and running.

## Running Chronos
Expand Down

0 comments on commit 9486587

Please sign in to comment.