Back

how devop works in appwrite

  • 2
  • Self Hosted
  • Tools
  • General
  • Databases
Suiii
17 Apr, 2023, 05:59

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

TL;DR
User is looking for an update on how DevOps works in Appwrite and shares a library they released. They mention the need for a way to export the Appwrite configuration. Another user suggests using migration scripts and maintaining a folder of them. Some users discuss the difficulties of keeping a local development instance and production in sync. The suggestion is made to manually update the production server with changes from the local development. There is a mention of a requirement for a staging area and syncing local changes to the production server. The solution for now seems to be manually making changes from local to production. The thread ends with a user asking for clarification on keeping the
joeyouss
17 Apr, 2023, 15:01

Hi - please see this about production: https://appwrite.io/docs/production

let me know your follow up questions

Suiii
18 Apr, 2023, 05:42

can you make it clear

Suiii
18 Apr, 2023, 05:42

it's not back up

Suiii
18 Apr, 2023, 05:42

but updating the new version from dev to pro env

darShan
18 Apr, 2023, 08:58

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).

Ipsoka
18 Apr, 2023, 10:38

So we would have to have a local setup and manually update prod with the new changes right

Suiii
18 Apr, 2023, 14:43

Thank you , exactly what you are saying

Suiii
18 Apr, 2023, 14:43

How does manual work ? Back up and restore ?

Suiii
18 Apr, 2023, 14:44

It makes sense to have local dev instance for testing before publishing to production

Ipsoka
18 Apr, 2023, 15:12

The problem im having is keeping both dev (local) and prod in sync

Suiii
19 Apr, 2023, 05:52

what is your workflow

Ipsoka
19 Apr, 2023, 08:56

I dont have a workflow yet, thats the problem

Ipsoka
19 Apr, 2023, 08:56

I just have one instance, that is prod

Ipsoka
19 Apr, 2023, 08:56

Since im not live yet, I can just wipe data, but once I go live im not sure how to handle dev and prod

Ipsoka
19 Apr, 2023, 09:00

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 (!)

Suiii
19 Apr, 2023, 14:07

Awww that’s quite hustle.

Drake
20 Apr, 2023, 17:25

long term, i recommend maintaining a folder of migration scripts that use the server sdk to manage your project.

Bouahaza
20 Apr, 2023, 19:03

I upvote it cause Appwrite lacks a real environment strategy

Bouahaza
20 Apr, 2023, 19:05

You have to do everything by hand (or via scripts), not the best for maintenance, collaborative work, CI/CD, etc.

Bouahaza
20 Apr, 2023, 19:06

just having a JSON (or other) export of the whole appwrite configuration would be a good thing

Guille
24 Apr, 2023, 20:38

I've released a library I'm using to sync two appwrite instances, I would appreciate any feedback

https://github.com/gepd/appwrite-sync

Suiii
30 Jun, 2023, 17:00

any update so far?

Reply

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