Skip to content

18.1.0
Compare
Choose a tag to compare
@elliotmatson elliotmatson released this 30 Jul 05:34
· 165 commits to main since this release
v18.1.0
12ff809
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

New Features

  • Added PGAdmin container to manage server #3, #4
  • Added healthchecks to all containers #7
  • Added automated testing via GHA #8
  • Created docker container to bootstrap PGAdmin #9

Updating

Backup your database before updating!

From v18.0.0

This should be a straightforward update from v18. Transfer over the values you modified to the new docker-compose.yml file, and run it!

From an older version

The Postgres container throws errors if it's updated without updating the database files, so a straight upgrade isn't possible. The best way is as follows:

  1. Save a database backup (or use one from the backup container)
  2. Destroy the old docker-compose stack
  3. Run the new docker-compose stack
  4. Import the backup in Resolve

You could also setup the new and the old versions at the same time (on different machines, Resolve requires that the Postgres server is on port 5432) and then use Resolve to transfer the files, but that's a bit more complicated

Full Changelog: v18.0.0...v18.1.0

Assets 2
Loading