@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.