Allow custom domains for development environments
under review
Muhammad Qureshi
Currently, the development environments have URLs like xyz.edward-nyc.servebolt.cloud. And when we add a custom domain to make it look presentable to the client, like xyz.agency.com (agency.com being our company website), it is counted as a production environment and the Bolt has to be paid for.
It wold be great if we are allowed to have development environments on agency's sub-domains. At least, the agencies in the Servebolt's Partner Program should be allowed to do this.
Log In
Thomas Audunhus | Acting CEO | Servebolt
under review
Thomas Audunhus | Acting CEO | Servebolt
Thank you for posting, Muhammad Qureshi! I have a few more questions for you:
- Can you provide more details on how you envision the process of adding custom domains to development environments?
- What are the potential benefits you see for agencies in the Servebolt's Partner Program with this feature?
- Are there any specific limitations or rules you would suggest for the use of custom domains in development environments?
Muhammad Qureshi
Thanks Thomas.
- No specific process. It can be like it is currently for adding domain to switch an environment from development to production.
- Some agencies would like to keep the names of the services (like Servebolt) they use hidden from their clients. When sharing an under-development website with the client, it looks more professional to share a URL that is like xyz.agency.com than xyz.edward-nyc.servebolt.cloud. This can also apply to the staging websites. For example, I have a staging/under-development version of a live website on Servebolt. The URL of that staging is testkl-23826.edward-nyc.servebolt.cloud. This looks very odd. I should be able to make it like stg.birttani.com or stg-birttani.qureshicreatives.com.
- To make sure people don't misuse this feature, you can put a limitation of number of days and the domain name on which the sub-domains can be added.