Replies: 7 comments 19 replies
-
Part of the discussion was about moving db data from a dev server to production. For that use case... You can backup and restore the MariaDB information using this tutorial: https://dev.to/appwrite/appwrite-in-production-backups-and-restores-4beg Part of that tutorial is making a MySQL dump of your data. You should be able to create a dump of your MariaDB data and then restore it the same way they do in that tutorial. I think the only thing missing to get that script working is just a command to dump the correct data. Instead of |
Beta Was this translation helpful? Give feedback.
-
A migration tool is something we would love to see. Both between different Appwrite instances, and from other platforms into Appwrite. One of the challenges is to understand the packaging format, potential dependencies between objects, the order of import, and how to scale the solution for very big exports. This is for sure something the core team would like to tackle. We will keep this discussion up-to-date with any progress we make. |
Beta Was this translation helpful? Give feedback.
-
Not sure if it is a right place to ask/discuss... What I am missing in Appwrite is tooling and documented preferred workflow for entire development & maintenance cycle available out-of-the-box. This includes:
I think my question may be closely related to "infrastructure as a code" concept. I'm a huge fan of fully automated release cycles, backups, migrations and infrastructure. So my main question is - are there any long term plans to design & implement such tooling and workflow in Appwrite? UPD: Just found an RFC for CLI 2.0 https://github.com/appwrite/rfc/blob/cli-2.0/018-cli-2.0/018-cli-2.0.md#-the-appwritejson-file. As I understand, CLI 2.0 will solve some cases I listed above. |
Beta Was this translation helpful? Give feedback.
-
Data Migrator Open SourcedThe Data Migrator is now officially open sourced. A lot of effort was put into making sure that this project provides real value to the Appwrite community and is built to scale well. I hope you appreciate it and the time it saves you. This is the first publicly available alpha version (so keep this in mind) however, the main use cases of uploading and migrating data from CSV to Appwrite works well. This app is targeting the need of uploading data into Appwrite first. Once some more of the core features are finished, data backup will also be implemented in the tool. The tool isn't far off already from being able to backup and restore database schemas as well. |
Beta Was this translation helpful? Give feedback.
-
In general, an official script for backing up and restoring an entire Appwrite instance would probably be very useful. In other words, a script that simply stores an SQL dump for MariaDB and a volume backup in the same folder and can then load everything from this folder back onto a new AppWrite instance. Then you only have to worry about a place for the backup and not about several scripts for the different Docker containers. |
Beta Was this translation helpful? Give feedback.
-
What is the best way to migrate from local instance to another server instance |
Beta Was this translation helpful? Give feedback.
-
There is a set of scripts which help to backup/restore data, dump |
Beta Was this translation helpful? Give feedback.
-
Based on a small conversation on discord and since this idea was mentioned a few times in the past, let's talk about appwrite migration tool idea.
A CLI tool that could:
Database:
Storage:
Same type of CLI tool for different languages/environments, like node.js, kotlin, PHP and others ... (write them in the comments, I don't know them all :D )
There could also be a UI-based, self-hosted tool for all of this.
If some member of the community is already working on some UI-based tool, it could be improved with these features.
Example of possible solutions: https://laravel.com/docs/8.x/migrations
Comment your thought, ideas, etc. :D
Beta Was this translation helpful? Give feedback.
All reactions