Multiple instances of same Project

I created an open-source project which is using Appwrite as a backend. I am using multiple instances that acts as development, staging and production environment. But everytime I do the change in one environment instance, I have to ship it manually to other instances. Is there a way to automate it?

Also need a system with which, other contributors can also migrate the configuration of the instance to their own Appwrite cloud account for developing features.

Multiple instances of same Project

Currently, you could use the Appwrite CLI to back up database schemas, Functions, storage bucket configurations, etc. You could then commit the resulting appwrite.json file to your repository, and other contributors could run the appwrite deploy commands to initialise their projects the same way.

This wouldn’t really help you with moving between your own projects, as appwrite deploy recreates the resources from scratch - so you’d lose all data in the database, storage bucket, etc

Another option (for yourself) is the Migration feature, which does keep all data when moving around.

There’s also a planned backups feature for some point in the future, which would allow you to export a Project to some kind of backup file, which could then be imported somewhere else. But that’s not really even at planning stage yet.

The best option you really have (right now) is to use appwrite deploy to create new instances of a project for new contributors, and to build your own migration scripts to help you move around between your own Projects.

Or write your own scripts that use a server SDK to perform any schema upgrades

That’s what I meant by your own migration scripts. I probably could have written that a bit better

Oops sorry missed that last part!

are there any articles or tutorials which I can follow?