Back
Appwrite Environments and database migrations
I am currently exploring the integration of Appwrite into a mobile application I'm developing using Flutter. Appwrite appears to offer a comprehensive suite of features that aligns with my project requirements. However, I am having one concern which I am not able to find an answer for. As the documentation suggests, importing database structural changes from one environment to another(for example from "dev" to "staging') seems to necessitate the creation of a script for repopulating or resynchronising the database, as the existing data would otherwise be erased. This leads me to two critical inquiries:
- Is the recommended approach to manage this migration via the Command Line Interface (CLI), which involves deleting the existing database and subsequently repopulating it? If there are alternative methods, I would appreciate any suggestions or best practices.
- How feasible is this approach in a production environment, particularly in terms of migrating content while the application is actively being used?
TL;DR
Developers are seeking advice on managing database migrations when using Appwrite in a mobile application. They want to know if the recommended approach is to use the CLI to delete and repopulate the database, and if there are alternative methods or best practices. They also want to understand the feasibility of this approach in a production environment with active users.
Solution: The recommended approach for managing database migrations in Appwrite is through the CLI. Deleting and repopulating the database is one way to handle structural changes. However, alternative methods or best practices are not mentioned in the thread. The feasibility of this approach in a production environment with active users is not