Hey Everyone, I had tried to implement DNS Based Multitenancy Server with AWS & Ubuntu 16.04.
Followed this Easy Install Tutorial and Everything gone perfect for production. Okay. There mentioned “Setup Production” and tried what Nginx Configuration was saying. But, Too confusing for the newbie. So, skipped. Although Everything is running well.
Now, I came to this where mentioned Guide to Setup Multitenancy. I preferred DNS based multitenancy instead Port based multitenancy, anyway everything gone perfectly. Created site for example : beta.domain.com
Still, everything perfect, got logged-in and had seen complete 10 steps ERPNext setup, which is normal. However, skipped for testing another site is working or not. Created another site, for example alpha.domain.com
Still there is no problem, get logged in. But a bit shocked there to see only 3 Steps setup wizard configuration at alpha.domain.com whereas I was willing to do like this. These are limited, while I want complete configuration wizard.
My will was: Every time I create new site like alpha, beta.domain.com. Each time I want to configure fresh setup for the client. I mean, completely different from one another. Also, I think backup will remain same if above thing happened. But, I want different backups for each different DNS.
What I think is: Database used for alpha, beta.domain.com, are common. This way, If I removed parent DNS or first site then each DNS based ERPNext will have vanished. I don’t want this. Don’t want to maintain any relation with alpha.domain.com & beta.domain.com They should be completely different from one another.
Screenshot Included here:
Plus, This thread’s question was about to ask regarding Cloudflare + ERPNext DNS based Multitenancy, already resolved at my end. But, still for others. This solution worked, but what in case if we use SSL(flexible or strict), what will happen? Brother, We had faced this issue along.