Christopher Vagnetoft
ec1659e96d
* Moved logic from entrypoint to a dedicated class. * Disabled automatic flush of state. * Added locking support to prevent multiple instances. * Added logging * Added base interface for CredentialsLoader
Fresh: Keeping your docker stacks up to date
Fresh was written to scratch an itch. It works by querying the respective repositories returning
Building
Build using NoccyLabs Pharlite.
Usage
To check for updates, pull updated images and recreate any containers defined in the
docker-compose.yml in the current directory:
$ fresh.phar
For all available options, use the --help flag.
Known Issues
- There is currently no way to update the state when manually updating using the
--checkflag. - Only checks authenticated registries for new versions. But if you are using this you probably aren't using DockerHub anyway.
Using the-qor--quietflags doesn't mute the output fromdocker-compose.- ~Using
--checkstill updates the state, need a--no-stateflag or so to ~prevent updating the state.
FAQ
- How does Fresh remember the last seen hash? The container hashes are stored
in the same directory as the
docker-compose.ymlfile in a file namedfresh.yml. Remove this file to force trigger an update.
Changes
0.1.1
- Moved the logic from the entrypoint script to its own class.
- Added locking (though
fresh.locklockfile) to prevent multiple instances. - Added
--afterhook to invoke script after update. - Disabled automatic flushing of the state to disk; --check will no longer update the state file, but --pull and default update will.