Keep Sync of Team

which means, if I prefer cli, I must go with it, it cant be syned

if I add or update field of collection in console , will it update to appwrite setting ?

Yes, you can pull down to add changes you made in Console to appwrite.json with appwrite init .... As long as you keep them in sync, you should be fine.

Essentially, appwrite.json will always overwrite anything in Console

right. any way to also get data?

For data, you'll have to write your own scripts, or use backup + restore.

okay right. so, when I pushed the appwrite.json to github, then other devs can pull and just manually appwrite deploy right

what about appwrite login , use their own local instance right

Yep

Yep

nice nice.

@ideclon then i link this question, how can i deploy the change to production serverx

You can do appwrite login again to switch which server you're connected to, then appwrite deploy ...

Seem similar but production contains data

Oh, but data, right

Yep

Workflow is like : local console update anything , init to appwrite setting . Then share to dev, then deploy to production server

I guess for now there's not really much option there. There's this Issue (https://github.com/appwrite/appwrite/issues/5586), which doesn't really seem to have any updates.

Then , i wonder how people out there deploying to production serverr

I would suggest creating migration scripts using a server SDK. You can take inspiration from existing DB migration systems

it should be generatable script by appwrite for standaradnizeness.

I see the appwrite.json is pretty handy for updating the collection schema, would it be better tool in the future to do migration, wihtout losing data.

@Steven

https://github.com/appwrite/appwrite/issues/5586

yes right. hope they will release in upcoming