Rank 3: Container
If I already have production project on server , and I keep working on development then what is the best way to keep the production server updates from the local development
To keep production data on updating
Votes
2
Replies
22
Participants
Unknown
Messages
23
Rank 3: Container
If I already have production project on server , and I keep working on development then what is the best way to keep the production server updates from the local development
To keep production data on updating
Hi - please see this about production: https://appwrite.io/docs/production
let me know your follow up questions
Rank 3: Container
can you make it clear
Rank 3: Container
it's not back up
Rank 3: Container
but updating the new version from dev to pro env
Rank 4: Virtual Machine
I think what @Suiii means is a requirement of staging area sort of thing for continuous development (local in this instance) where any change does not affect the production instance until and unless it is published / released to production. More like syncing/pushing local changes to production server.
I believe there was an issue for this but I couldn't exactly find it.
For now, it seems you'll have to manually make changes from local to prodn (afaik).
So we would have to have a local setup and manually update prod with the new changes right
Rank 3: Container
Thank you , exactly what you are saying
Rank 3: Container
How does manual work ? Back up and restore ?
Rank 3: Container
It makes sense to have local dev instance for testing before publishing to production
The problem im having is keeping both dev (local) and prod in sync
Rank 3: Container
what is your workflow
I dont have a workflow yet, thats the problem
I just have one instance, that is prod
Since im not live yet, I can just wipe data, but once I go live im not sure how to handle dev and prod
The only plausible way I can see right now is versioning the appwrite - folder (without .env, this you should copy manually) and manually apply all changes to prod once tested in dev. This means you'd have to manually recreate e.g. your functions on prod with the same id (!)
Rank 3: Container
Awww that’s quite hustle.
long term, i recommend maintaining a folder of migration scripts that use the server sdk to manage your project.
Rank 4: Virtual Machine
I upvote it cause Appwrite lacks a real environment strategy
Rank 4: Virtual Machine
You have to do everything by hand (or via scripts), not the best for maintenance, collaborative work, CI/CD, etc.
Rank 4: Virtual Machine
just having a JSON (or other) export of the whole appwrite configuration would be a good thing
Moderator
I've released a library I'm using to sync two appwrite instances, I would appreciate any feedback
Rank 3: Container
any update so far?