-
Notifications
You must be signed in to change notification settings - Fork 1
Artifact recovery #1
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
base: main
Are you sure you want to change the base?
Conversation
fix postgres and backup collection
* bump version to 0.20.53; pin redis * pin redis to 5.2.0
* fix s3 proxy * format code * pin websockets * websockets>=14.0 * allow sharedarraybuffer * Improve getting started
* support load balancing * Update workspace.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, thanks for the PR, could you move the artifact-recovery scripts to utils folder instead of a separate one, there we already have the backup_database.py
Is there a command for dry-run the script without causing any damage, but check if the script working?
Will do! |
@oeway I moved the files to util/ and using only Claude I added the option --dry-run, but I haven't been able to test it fully because I lack the necessary environment variable values. Upon inspection, however, I think it looks pretty good |
OK, thanks! I think you can test it in the juptyer notebook we used to perform recovery, that has already env there. |
No description provided.