What do you think about moving to keys into Postiz DB

[nevo-david]

I know many people want a docker compose but they would still need to edit the .env file to add providers every time.

I can be a lot easier if it could be managed from the DB, from the dashboard with a super admin user.

It does put a bit of security holes that we will need to think about

[jamesread]

Hey, superb idea, I was absolutely going to suggest the same.

I totally appreciate you are transitioning this project from a SaaS to a Self-Hosted service, and that means you're having to reverse-engineer several bits to make them more friendly to self-hosting.

Generally, self-hosters like to have as few dependencies as possible, and even better, as few dependencies on "cloud-only" services and this will then /really/ appeal to self hosters even more!

On top of that, having to edit the .env settings file, stop and start the app makes configuration quite cumbersome.

I absolutely don't understand the whole architecture yet, but I'd suggest;

• Try to get down to one database only - postgres or redis - those are both easily self-hostable. Probably Postgres is best as many people will be running that already.
• Consider making CloudFlare R2 storage optional, I don't understand what is being stored there yet, but if it's configuration/data, put that in Postgres, if it's blobs, then just save those on the local filesystem.
• Consider switching Resend /email to no-email (I see there is a pull request open for this already).

That's a lot of architecture work, and I don't want to go too far, but a simple settings editor to save settings in Postgres would be a hugeee step forward and a great foundation for the future. One extra huge benefit you'd get from this is being able to validate setting values (check that URLs don't end with a /, or that it is a valid Postgresql schema, etc). At the moment, editing the .env file is kind of error-prone as you're not sure if you're entering the value in the right format.