-
Notifications
You must be signed in to change notification settings - Fork 7
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
Self hosted PostgresDB + Timescale extension + Regular data backups + Destroy github actions #2
base: main
Are you sure you want to change the base?
Conversation
update to use python version 3.6 instead of 3.5.12 for available-solution-stacks
…ployment of self hosted timescaledb
@romer8 Thank you for working on these features, and apologies for taking awhile to review this. We're still formalizing our contribution guidelines here, but could you create a couple issues for these new features for discussion, and maybe split this into two issues/PRs, one for everything related to the self-hosted Timescale feature, and another for the action to tear down an AWS HydroServer environment? That will help keep these on our milestone radar so we don't lose track of them, and help me review these features independently from each other. We'd definitely like to get the destroy action merged in, and I think the self-hosted Timescale will be a useful feature, but we may want to get some additional feedback on that one from Jeff and Daniel. |
I think there is a lot of possible improvements for the PR, but after doing a couple of trainings seems that alot of people really want to be able to host their own timescale db