Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: add upgrade process to README #198

Merged
merged 8 commits into from
Nov 24, 2022

Conversation

jayaddison
Copy link
Contributor

@jayaddison jayaddison commented Nov 24, 2022

Todo:

  • Follow the documented upgrade instructions here for an existing container, and apply any corrections necessary

@jayaddison
Copy link
Contributor Author

From searching around in the grocy code: it includes an update.sh script: not all of that's relevant (or straightforward) in a container environment, but perhaps it'll be possibly to unify an approach at some point so that the same steps are followed regardless of container/non-container deployment.

@jayaddison
Copy link
Contributor Author

I practised using these guidelines to upgrade a local containerized Grocy instance from v3.3.1-6 to v3.3.2-0, and that seems to have succeeded ✅

While setting up the test containers for v3.3.1-6, I did skip some of the 'official' Docker volume backup/restore steps (because I think it's ridiculous to run an entire container simply to copy some files, as mentioned in #196) -- and after doing that, ran into some login-time errors due to stale viewcache data. Removing the viewcache directory, and ensuring the correct file permissions solved the problem.

@jayaddison jayaddison merged commit 1e28763 into main Nov 24, 2022
@jayaddison jayaddison deleted the documentation/upgrade-process branch November 24, 2022 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant