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

Backup best practice #782

Open
zimski opened this issue Oct 8, 2024 · 2 comments
Open

Backup best practice #782

zimski opened this issue Oct 8, 2024 · 2 comments
Labels
documentation Improvements or additions to documentation

Comments

@zimski
Copy link

zimski commented Oct 8, 2024

From the first time I used the solution, I noticed that for Hetzner, no backup was installed because the provider doesn't support S3.

I get it, but :) :

  1. I think it's a good practice to encourage the users to backup the database outside of the provider that hosts the cluster
  2. Now Hetzner supports S3 (Beta for now)

The 1. implies that we need a form when setting up the cluster to set up the S3 credential and endpoint.
The advantage is that this allows the user to host the backup wherever they want, ideally with a different provider.

If this aligns with your vision of the product I can prioritize some times to do the dev as we need this to go into production with your solution.

@vitabaks
Copy link
Owner

vitabaks commented Oct 8, 2024

I completely agree with you. We plan to add to the “Expert mode” the ability to configure backup settings to be able to specify the necessary options (e.q., AWS S3).

Currently, this can be done via the command line, but not yet in the UI.

@vitabaks
Copy link
Owner

vitabaks commented Oct 8, 2024

Now Hetzner supports S3 (Beta for now)

Thanks, I'll take a look at it.

@vitabaks vitabaks added the documentation Improvements or additions to documentation label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants
@zimski @vitabaks and others