-
Notifications
You must be signed in to change notification settings - Fork 227
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: Backup and restore #83
Comments
Regarding this, probably what's mainly fundamental is:
It's possible to backup everything by stopping everything and copying everything, but since that affects availability, it's not a good approach Apart from this, I find it very useful to have the following:
|
@DH-555 Thanks for the suggestion! |
Hey @gewenyu99 Can you assign it to me? I wanna try it out |
Awesome! I have assigned you @Susmita-Dey Notes: Please update us with your progress every 3 days, so that we know that you are working on it. Cheers |
Hey @gewenyu99 I guess you forgot to do it under the assignees section |
I blame github's API! (maybe I forgot |
Update: Started working on it! |
Feel free to share the outline to get it reviewed |
Closing issue due to inactivity, thank you for taking the time to be part of hacktoberfest this year :) |
💭 Description
The Appwrite community has vast knowledge and expertise in managing Appwrite instances. The community has self-hosted larger Appwrite instances in production, and you can share your knowledge in backups and restores with the community, here.
Goal
Provide guidance on managing backups and restores for self-hosted Appwrite instances.
Content
Should contain scripts and examples of backup and restore procedures for self-hosted Appwrite instances.
Should be contributed to the
src/routes/docs/tutorials
folder.How to contribute
Pitch an outline detailing each page you plan to add and headings within, and ask to be assigned. Open a PR after the outline has been approved.
The Appwrite team will collaborate with you on the outline and PR.
Thanks for taking the time to make our documentation better 🙏
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: