topaz cave
I am a team of only 3 devs, we use local dev docker in each machine, how can we keep sync what has been changed by each person, I know backup and restore, but it is quite husstle.
Any suggestion or recommendation. Cloud is but we do not want to use cloud
lament widget
I am a team of only 3 devs, we use local dev docker in each machine, how can we ...
You’re wanting to keep data in sync between you, or project structures?
topaz cave
You’re wanting to keep data in sync between you, or project structures?
only the project structure. I have an thinking when creating / update collection structure to write script file. But, it should be generated automattically.
lament widget
only the project structure. I have an thinking when creating / update collection...
You can use appwrite init … and appwrite deploy … to save and read from an appwrite.json file.
Note that deploying a Collection currently wipes all data in the collection, but this is intended to change.
You can use a seed script to seed data in those blank Collections once you’ve deployed them.
topaz cave
You can use `appwrite init …` and `appwrite deploy …` to save and read from an `...
also make sense, but better to have way to keep data
topaz cave
You can use `appwrite init …` and `appwrite deploy …` to save and read from an `...
inside appwrite docker fodler?
lament widget
inside appwrite docker fodler?
In your project directory
topaz cave
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 ?
lament widget
if I add or update field of collection in console , will it update to appwrite s...
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
topaz cave
right. any way to also get data?
lament widget
right. any way to also get data?
For data, you'll have to write your own scripts, or use backup + restore.
topaz cave
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
lament widget
okay right. so, when I pushed the appwrite.json to github, then other devs can p...
Yep
lament widget
what about appwrite login , use their own local instance right
Yep
topaz cave
nice nice.
@lament widget then i link this question, how can i deploy the change to production serverx
lament widget
<@796164927034359808> then i link this question, how can i deploy the change to ...
You can do appwrite login again to switch which server you're connected to, then appwrite deploy ...
topaz cave
Seem similar but production contains data
lament widget
Oh, but data, right
topaz cave
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
lament widget
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.
topaz cave
Then , i wonder how people out there deploying to production serverr
tepid rover
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
topaz cave
I would suggest creating migration scripts using a server SDK. You can take insp...
it should be generatable script by appwrite for standaradnizeness.
topaz cave
I would suggest creating migration scripts using a server SDK. You can take insp...
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.
@tepid rover