v18.1.3

What's Changed

• Bump docker/metadata-action from 4.0.1 to 4.1.0 by @dependabot in #21
• Bump docker/login-action from 2.0.0 to 2.1.0 by @dependabot in #22
• Bump docker/build-push-action from 3.1.1 to 3.2.0 by @dependabot in #23
• Bump docker/metadata-action from 4.1.0 to 4.1.1 by @dependabot in #24
• typo correction by @Marc-Wang in #25
• Corrected some small things of README.md by @Akronix in #27
• Bump docker/metadata-action from 4.1.1 to 4.2.0 by @dependabot in #28
• Bump docker/build-push-action from 3.2.0 to 3.3.0 by @dependabot in #29
• Bump docker/metadata-action from 4.2.0 to 4.3.0 by @dependabot in #30
• Bump docker/build-push-action from 3.3.0 to 4.0.0 by @dependabot in #32

New Contributors

• @Marc-Wang made their first contribution in #25
• @Akronix made their first contribution in #27

Full Changelog: v18.1.2...v18.1.3

18.1.2

Added config creator container to Docker Hub under elliotmatson/pgadmin-config-creator

What's Changed

• Bump docker/build-push-action from 3.1.0 to 3.1.1 by @dependabot in #18
• Bump docker/login-action from 1.10.0 to 2 by @dependabot in #20

Full Changelog: v18.1.1...v18.1.2

18.1.1

What's Changed

• Create LICENSE.md by @elliotmatson in #16
• Fix pgadmin4 by avoiding volume overriding default directory by @greigdp in #17
• Fix config-generator overwriting config file every launch

New Contributors

• @greigdp made their first contribution in #17

Full Changelog: v18.1.0...v18.1.1

18.1.0

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

18.0.0

Updated PostgreSQL and PGBackup containers to v13 to match updates in Resolve 18. Using this with Resolve 17 or older might work, but is not recommended.

17.0.0

This is a version compatible with Resolve versions before v18.0. Newer releases should function for basic project storage, but other database functions in the Resolve Project Manager UI might not work, such as restoring a backup and vacuuming.