Isolate SMTP Settings from Source code repo, or tie them to APP ID

[yahiakalabs]

Building on this:

Changing SMTP settings creates a commit

What I’m trying to do: Collaborate on an open source app where each developer/clone has their own SMTP settings. What I’ve tried and what’s not working: I cloned an app from GitHub and then added custom SMTP settings. This created a commit. Suggestions I suppose there are two options here: Tie the SMTP settings to the APP ID like you do with secrets Isolate the SMTP settings from the git repo like the environments and databases I prefer Option 2 as, ultimately, I don’t want to create com…

The current behaviour makes it messy for me to collaborate on an open source project where each collaborator has different SMTP settings. So my workaround has been to use the open source app as a dependency app, and have a second app to configure deployment stuff like SMTP settings and users service settings (that’s another story).

I really think the SMTP settings fall under ‘deployment settings’ like the deployment URLs and such, and are out of place in the code repository itself.

I suppose you could tweak it like you tweaked the anvil secrets (to save SMTP settings tied to app IDs) and if that’s more achievable for the Anvil team, I’ll take it!