Yes, you can add new domains to Cloudron. Depending on where the authoritative servers are for the domain, you can use the dedicated API-based setups (i.e. AWS, DO, Namecheap, Linode, etc), or you can instead use the Wildcard setup for any other service that's not explicitly listed in the providers list.
I suppose each Cloudron needs a unique domain name because of the DNS records that are being created when installing a Cloudron: DKIM, SPF, DMARC?
Yes, and also because we need a unique location to access the dashboard.
what if the domain that's being used for a Cloudron already has e-mail related DNS records, for example when it's already configured for use with G Suite or Office 365? Will Cloudron modify those records, override them or just ignore them?
If you have an existing DMARC, it don't touch it. Otherwise, it will put the default strict DMARC policy. DKIM uses a unique selector domain, so it won't affect other DKIM entries. The SPF is modified with "a: my.<domain.com" into the existing SPF.
@nebulon there was no error reported by cloudron. The issue was that if I tried to curl, there was nothing returned back (I don't remember the exact reply -- sorry for that). Basically it was like nginx was not routing properly, as if nothing was running at the subdomain.
@girish Im tracking with what you saying but the API didn't create any A records. In fact i couldn't get to the dashboard at all until i created that * wild card. I still have no idea why its not redirecting to HTTPS if i put int http://www.mydomain.com. The only files the API created in dns were 2 txt records and a testcloudrondns at 127.0.0.1
@robi yeah, with ecommerce being our primary business, we're invested in this. We have 12 very experienced devs on the team but just a few of them have had time to start looking at Cloudron this week. In this for the long-term though so I'm sure you'll start to see our work filtering through very soon.
I'm with @nebulon, I see this as difficult to support, harder to code for - and more user friction. I usually never support more user friction unless it's dire. I think configuring after installation is more than acceptable. It's not like we can't write scripts using their API to macro your suggestion too, but I digress. 😂
@atrilahiji I use Namecheap too, decent service but equally the Cloudflare free DNS services is pretty solid and not had any trouble with that & Cloudon. Just mentioning in case you got stuck or hadn't compared that option.
@girish yes, that’s a much better idea. Essentially the ability to “swap” app instances, or in other words the ability to easily promote from staging app instance to production app instance on the same server. That’d be ideal. 🙂
@davisdre The feature is available. Linode DNS is only not available in the initial Cloudron setup screen. This is only because user's were complaining nothing is happening for 15 minutes when they use Linode DNS.
You can later go to Domains view and change it from wildcard to Linode DNS.