@andre-dietrich By default, Edrys will store all instance data in the file system in a local directory. This is not allowed by services such as Deno Deploy or Cloudflare Workers. Instead, in this scenario you should configure Edrys to use S3 - which will make it store data in any S3 compatible API (AWS S3, self hosted Minio, Backblaze, CF C3 etc.) instead of locally on the file system. This will make it so you can run your Edrys from anywhere and as long as you point it to the same S3 endpoint, you will have the same instance with all your classes there.
Have a look at the configuration options here to get started: https://github.com/edrys-org/edrys/blob/main/docs/Deployment.md#data-storage
Let me know how it goes for you..
When using Deno Deploy don't modify these variables, the default should work. Here is an example that will work:
dist/app.jsfile from GitHub (main branch, automatic)
dist/static(this allows the frontend to be served correctly directly from GitHub)
s3(and then set all the appropriate S3 env vars) OR to set it to
memory, which is good for testing, it will use in-memory storage (so obviously all classes and accounts will be gone if the server isolate restarts)
Note if you haven't set up email sending env vars, you will have to look at the live logs to get the login code.