hosting/mash-playbook
1
0
Fork 0
Code Pull requests Activity

Update CHANGELOG.md

Browse source
This commit is contained in:
Slavi Pantaleev 2023-03-29 16:22:41 +03:00 committed by GitHub
parent 9e4e578f17
commit beedda826a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
CHANGELOG.md
View file

@ -2,16 +2,14 @@
## (Backward Compatibility Break) Firezone database renamed ## (Backward Compatibility Break) Firezone database renamed
If you are running firezone with the default postgres integration the playbook automatically created the database `mash-firezone`. If you are running [Firezone](docs/services/firezone.md) with the default [Postgres](docs/services/postgres.md) integration the playbook automatically created the database with the name `mash-firezone`.
To follow the naming scheme we now renamed it just `firezone`. You will have to rename you database manually by running the following commands on your server To be consistent with how this playbook names databases for all other services, going forward we've changed the database name to be just `firezone`. You will have to rename you database manually by running the following commands on your server:
```bash 1. Stop Firezone: `systemctl stop mash-firezone`
systemctl stop mash-firezone 2. Run a Postgres `psql` shell: `/mash/postgres/bin/cli`
docker exec -it mash-postgres psql -U root 3. Execute this query: `ALTER DATABASE "mash-firezone" RENAME TO firezone;` and then quit the shell with `\q`
ALTER DATABASE "mash-firezone" RENAME TO firezone;
```
Then run `just install-all` and you should be good to go! Then update the playbook (don't forget to run `just roles`), run `just install-all` and you should be good to go!
# 2023-03-26 # 2023-03-26