Devops and migration schemas management for production

Anyone has suggestions on migration management with appwrite

I am going to have one app that will have different isolated deployment. So I need to have updated changes for example script or whatever to apply to different appwrite database projects.

One option is manual updating on console but if i have many more it will be painful.

Something generated script to click to apply production appwrite schema to different projects

TL;DR

Using the CLI tool and the appwrite.json file is helpful for managing migration schemas in production. It should be safe to use appwrite push to database for schema changes, but it doesn't guarantee transactional behavior. In the case of deploying many changes like V2 in production, generating a script for applying changes as raw SQL is a practical workaround not mentioned in Appwrite documentation.

<:appwritepeepo:1156975874852270110>

Can you use the cli tool and the appwrite.json file?

yes that is very helpful tool. if in production we have production data. and there is changes in schema. is it safe to use appwrite push to datababae?

I think it should be fine, but it doesn't look like it uses transacations so I guess you could get into an instance where some items deploy but not everything.

if it already production, and you have alot of changes need to deploy like V2 . what step are you taking into actions? if it were to be raw sql, I generate changed script to apply. but i cannot find pratical way in appwrite document mentioned

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more

Recommended threads

Need support?

Join our Discord

Get premium support