Fermentrack was originally designed to allow “hot” updates by re-pulling itself from GitHub when a user clicked a prompt inside the Fermentrack UI. This worked as behind-the-scenes Docker was persisting the (temporary) volume containing the updated code. Unfortunately, this was apparently unintended behavior in Docker as I’ve found more recent installations lose these updates when the container (or container host) restart. As a result, I am going to have to retire the in-interface upgrades in favor of using dedicated fermentrack-tools upgrade scripts.
Fermentrack was originally designed to allow “hot” updates by re-pulling itself from GitHub when a user clicked a prompt inside the Fermentrack UI. This worked as behind-the-scenes Docker was persisting the (temporary) volume containing the updated code. Unfortunately, this was apparently unintended behavior in Docker as I’ve found more recent installations lose these updates when the container (or container host) restart. As a result, I am going to have to retire the in-interface upgrades in favor of using dedicated fermentrack-tools upgrade scripts.