Existing data is lost each time I deploy manifest.

[SebConejo]

Describe the bug
When I redeploy Manifest, I lose all the existing data. This is normal for a local environment, but annoying in production.

To Reproduce

1. Deploy manifest on any app platform (I chose Render when I discovered this issue)
2. Add content to your app
3. Relaunch a Deploy from render.io.
4. You will notice that you lost everything, even your admin account.

Expected behavior
I like this behavior in local environment. But it's dangerous for production. For preproduction it depends. Maybe the good DX would be to set an environment variable for local and preprod envs. This varialbe allows you to choose whether you want to expose the data, or leave the existing one.

[Shub3am]

Proposing a Solution to use Environment Variables to avoid this issue

[brunobuddy]

@Shub3am can you give more infromation ?

[brunobuddy]

@SebConejo Render.com web services do not offer data persistence. They seem to use some AWS stateless service to run the apps. They also offer storage and managed db but we have to configure it manually: https://render.com/docs/disks

[SebConejo]

@brunobuddy Okay so what are the technical solutions? Should we remove it from the doc, leave it as is? Add a warning message ? Other Solutions ?

[anurag]

@brunobuddy You can attach a disk to your Render web service and it will persist data across deploys. We don't use AWS stateless services; we've built our own.

[brunobuddy]

@anurag thanks for your message, it seams that ChatGPT still believes that render.com is a layer over AWS

@SebConejo I guess we should put a warning message for now and accelerate the statelessness of Manifest to be able to extract the storage from the service

[grinnellsec]

I believe the same occurs for DigitalOcean as well, if anyone could confirm. Does anyone know of services which have persistence?