Is there a way to export / transfer Appwrite project, including it's data to another server?

Suppose I have Appwrite project in one server and want to transfer it to another server. Everything is running on Docker. Would it be enough if simply just create a snapshot of the directory volume mounted in Appwrite?

TL;DR

The user is asking if there is a way to export and transfer an Appwrite project, including its data, to another server. The user mentions that there is a code available on GitHub for syncing two Appwrite instances. They also mention the need for a logic for managing different environments and the ability to add fields or make changes on one environment and have them automatically synced to others. There is a mention of migration and backup/restore. The user asks about importing data from an old server and suggests creating a snapshot of the directory volume mounted in Appwrite. It is suggested to review and upvote some relevant GitHub issues. Solution: The support

I transferred all the containers using docker save… and imported with docker load, but when I finished and deployed I don’t see the data🥲. How can I import the data from the old server?

You can use this gist https://gist.github.com/Meldiron/47b5851663668102a676aff43c6341f7

+1, without need to have docker access

You mean in an in-browser format?

If so, you can upvote this issue https://github.com/appwrite/appwrite/issues/5208

JSON, YML, whatever format

Sorry, didn't got you What you mean JSON, YML etc? for what part of the data you're referring?

Like ORM (for database) or like docker about buckets, etc.. Already explain that needed to core team btw Need real CI logic on appwrite

Okay 👍

Here is about backup/restore

And here migration

What about, you've 4 differents env (dev - stagging - production - archive), with differents data on each. You add fields (or whatever) on dev env, for now you need to manually add it on others env. You don't have historic, don't know from where this new fields come, etc... Need a logic here 🙂 I hope it is better explained this way