Komodo v1.14.1

• Stacks: No longer force deletion of stack folder when using UI defined compose file contents. It is still recommended to use docker volumes or absolute mount paths, and NOT mount anything inside the stack folder. Repo based stacks must still be deleted, in order to ensure fresh reclone is always possible without deleting needed data ie mounts. See #68.
• Stacks: Adds feature to docker compose build before compose down / compose up. This allows users to build in the compose file (say you are using a git repo containing Dockerfile), and still minimize down time. Complete with custom "Build Extra Args" which support Variable / Secret interpolation.
• Stacks: Adds option to disable automatic docker compose pull before compose down / compose up. Users which want to do this can manage pulling using pull_policy in their compose files. - #64 - @FibreTTP
• Stacks: Fix an issue showing latest file contents when using "Files on Host", but the UI "File Contents" still holds some outdated file contents. - @mmartial
• Repos: Fix PullRepo broken when using a custom clone path.
• Stacks, Deployments, Repos, Builds, Servers: Configure custom "Links" which are displayed in the resource header, and provide a quick link to the URL in a new tab.

Upgrading

To update, just compose down-compose up Core, update periphery using the systemd installer (or use the latest Periphery container image). Api is backward compatible with 1.14.0 (besides new features) so it doesn't matter the ordering you update.

When you upgrade Komodo, be sure to open your browser console/dev-tools, go to network tab, disable cache, and the reload page with dev-tools open. Otherwise, your browser may keep using a cached version of the old UI version.

Thanks to everyone involved in this release, your feedback has been invaluable.

Enjoy 🦎