Skip to content

NO_JIRA correct stack restart commands #97

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.

Sign up for GitHub

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

Merged
emyers-ccdc merged 2 commits into from
Mar 11, 2026
Merged

NO_JIRA correct stack restart commands #97

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f8c1155
NO_JIRA correct stack restart commands
emyers-ccdc Mar 11, 2026
6a34629
NO_JIRA add miss
emyers-ccdc Mar 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 16 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -241,12 +241,22 @@ docker compose ps
```

which should show the state of the services to all be `Up`. If any services have the state `Up (unhealthy)` or `Exit` then restart the stack.
Take care to include the right config files as in the commands below.
In most cases it is best to leave the postgres server running as in the commands below.

```sh
# Include docker-compose.insecure-configuration.yml if using a self-signed certificate
# Omit docker-compose.postgres.yml if self-hosting your postgres server
docker compose -f docker-compose.yml -f docker-compose.ssl.yml down
docker compose -f docker-compose.yml -f docker-compose.ssl.yml up -d
```

If the csd-database container is unhealthy then do a full restart of the stack and bring it up before the other containers.

```sh
# Follow the above instructions instead if using a self-hosted postgres server
# Include docker-compose.insecure-configuration.yml if using a self-signed certificate
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml down

docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml up -d csd-database
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml up -d
```

Expand Down Expand Up @@ -325,10 +335,9 @@ To change your license key you must delete the license volume and restart the st

```sh
# Include docker-compose.insecure-configuration.yml if using a self-signed certificate
# Omit docker-compose.postgres.yml if self-hosting your postgres server
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml down
docker compose -f docker-compose.yml -f docker-compose.ssl.yml down
rm -r lic
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml up -d
docker compose -f docker-compose.yml -f docker-compose.ssl.yml up -d
```

## Updates
Expand All @@ -354,10 +363,9 @@ For major releases export any in-house databases, recreate the csd-database and

```sh
# Include docker-compose.insecure-configuration.yml if using a self-signed certificate
# Omit docker-compose.postgres.yml if self-hosting your postgres server
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml down
docker compose -f docker-compose.yml -f docker-compose.ssl.yml down
docker compose pull
docker compose -f docker-compose.yml -f docker-compose.ssl.yml -f docker-compose.postgres.yml up -d
docker compose -f docker-compose.yml -f docker-compose.ssl.yml up -d
```

Now from lattice -> database management, reimport your in-house databases.
Expand Down