-
Notifications
You must be signed in to change notification settings - Fork 385
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
Cronicle upgrade doesn't work with a custom installation path #778
Comments
Yeah, Cronicle really wants to live in I'm really sorry you ran into this. I'll add a louder mention of this in the docs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Cronicle upgrade doesn't work with a custom installation path. We've installed cronicle at a custom path "/path/cronicle". However, when
/path/cronicle/bin/control.sh upgrade
is executed, it initiates a fresh install in /opt/cronicle directory.Steps to reproduce the problem
/path/cronicle/bin/control.sh upgrade
Your Setup
Operating system and version?
Rocky linux 8.7
Node.js version?
v16.20.2
Cronicle software version?
0.9.45
Are you using a multi-server setup, or just a single server?
1 Master and 3 workers
Are you using the filesystem as back-end storage, or S3/Couchbase?
Filesystem
Can you reproduce the crash consistently?
Yes
Log Excerpts
The text was updated successfully, but these errors were encountered: