8000 Give more background to infrastructure changes on release 2025.2.0 #569 by fernandinand · Pull Request #570 · MerginMaps/docs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Give more background to infrastructure changes on release 2025.2.0 #569 #570

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

Merged
merged 2 commits into from
Feb 28, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,4 +8,4 @@ services:
working_dir: "/docs"
command: /bin/sh -c 'yarn install && yarn dev'
ports:
- 8080:8080
- 8081:8080
21 changes: 16 additions & 5 deletions src/server/upgrade/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,20 +16,31 @@ Get the latest <GitHubRepo id="MerginMaps/server/blob/master/docker-compose.yml"
Perform the migration:

<MigrationType type="EE" />
::: tip Before you upgrade!
Release 2025.2.0 brings significant changes on <MainPlatformName /> docker compose orchestration infrastructure.

1. Double check if below environment variables are available and filled in `.prod.env` environment file. If not, add them.
Previous individual `server` container is replaced by 3 service dedicated containers that split the core components of <MainPlatformName />, `server-gunicorn` the app, `celery-beat` Celery task scheduler and `celery-worker` a dedicated worker container for Celery tasks.
:::

1. Stop your running docker containers and build the new images
```bash
$ docker compose -f docker-compose.yml down # or similarly, based on your deployment
# INFO: After shutdown update the docker-compose.yml file to latest release
```

2. Double check if below environment variables are available and filled in `.prod.env` environment file. If not, add them.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. Double check if below environment variables are available and filled in `.prod.env` environment file. If not, add them.
2. Double check if these environment variables are available and filled in `.prod.env` environment file. If not, add them.


```bash
SECURITY_EMAIL_SALT='<YOUR STRONG HASH>'
SECURITY_BEARER_SALT='<YOUR STRONG HASH>'
```

2. Start up your docker containers
3. Start up your docker containers
```bash
$ docker-compose -f docker-compose.yml up # or similarly, based on your deployment
$ docker compose -f docker-compose.yml -d up # or similarly, based on your deployment
```

3. Check that you are on correct versions (`07f2185e2428`, `df5b4efdae7b`).
4. Check that you are on correct versions (`07f2185e2428`, `df5b4efdae7b`).
```bash
$ docker exec merginmaps-server flask db current
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
Expand All @@ -44,7 +55,7 @@ Perform the migration:
$ docker exec merginmaps-server flask db stamp df5b4efdae7b
```

4. Run the database migration:
5. Run the database migration:
```bash
$ docker exec merginmaps-server flask db upgrade community@ba5051218de4
$ docker exec merginmaps-server flask db upgrade enterprise@ba5ae5972c4a
Expand Down
Loading
0