* fix: Update description for hobby upgrade script
In the original warning's language (written by yours truly), I don't mention which version number nor which dates are relevant to the issue.
[x] Added a check to see if the containers exist or not (`docker volume ls | grep -Pzoq 'root_cl2ickhouse-data\n(.|\n)*root_postgres-data\n'`)
[x] Added the dates and version number now allows users to better understand if the warning is relevant to them.
[x] Minor improvements to the language and instructions
* feat: track warning states for better user prompts
Use state from pre-update volume presence check to show post-install warning about data loss in addition to pre-upgrade warning.
* Improve references to docker container names
Previously instructions erroneously included my particular instance's containing folder. Changed grep check and added 'wildcards' in the instructions to clarify that it might be named differently depending on the environment.
We are running yarn install and starting the frontend dev server for
hobby. This isn't necessary or desired as the image is prebuilt.
Note we also need to update the /compose/start as well, in the upgrade.
It could probably do with a refactor but I'm not going to do that now.
* Add persistent volumes to docker-compose-hobby
Per the discussion in https://github.com/PostHog/posthog/issues/10792, implemented the "Kessel Fix" in less than a parsec.
* Add warning text to user prompts to avoid data loss
Following discussion with PH team, we wanted to give users the information needed to properly manage the data in their installation and avoid potential data loss.
* chore(hobby deployments): various fixes
* default do not check versions for current hobby release
Co-authored-by: James Greenhill <fuziontech@gmail.com>
