Store DNS provider keys

[ekevu123]

I host most of my domains in one Porkbun account, but this would work similarly for any other provider. For any new domain I add, I need to find again the API key and secret key and add it. If they ever change, I need to change them for all domains separately.

Idea: Store the secrets separately, and allow the user to change/update them in one place. This would be optional, and the user could still use separate API keys per domain, but I think we can assume that one would want to use the same pair of keys for the same account in Cloudron.

Besides, the values are stored already anyway if they are in use, so this changes only the underlying database structure and the UI.

[joseph]

Not directly related but a clone action for various resources like Backup Sites would be useful . (or you could clone a domain like your usecase)

[ekevu123]

Not sure if cloning is exactly UI-friendly here. The user intention is to add another domain, which is a separate action than cloning. You'd assume you perform an action that is separate from other domains, I'd say.

For backup sites, I am more with you: There it makes more sense to use the same site, but change a detail.