after few initial problems which we managed to solve, there is one left.
We can have only domain.com address, because when pointing to a server using www.domain.com we're getting accelerator page, not umbraco.
So, question is - is there any way of having umbraco serving multiple domains (I will need different domains also soon) and with and without "www" for a single domain on a single deployment of Umbraco.
If the domain issue is only regarding domain.com with and without www then I would make sure to use www.domain.com when setting up the site in azure and the use dns to forward non-www domain.com to www.domain.com. But that being said you would run into an issue with Umbraco on Azure if you wanted to add blog.domain.com to that same site. The reason being that the Accelerator uses the name of the folder (under sites in your blob storage) as binding for the site, which is automatically generated on your Azure instances. This poses some limitations, which I created a workaround for. In order to use the workaround you will have to add some code to the web role of the accelerator, which is explained here:
Thank you for your answer Morten! We had to do some minor modifications to your solution due to different versions of accelerator, but your example was what we needed to get started.
Domain problem when deploying on Azure using accelerator
Hello everyone,
after few initial problems which we managed to solve, there is one left.
We can have only domain.com address, because when pointing to a server using www.domain.com we're getting accelerator page, not umbraco.
So, question is - is there any way of having umbraco serving multiple domains (I will need different domains also soon) and with and without "www" for a single domain on a single deployment of Umbraco.
Thank you in advance!
Any help guys? Still unable to resolve a problem and deadline is looming. :(
Hi Almir,
If the domain issue is only regarding domain.com with and without www then I would make sure to use www.domain.com when setting up the site in azure and the use dns to forward non-www domain.com to www.domain.com. But that being said you would run into an issue with Umbraco on Azure if you wanted to add blog.domain.com to that same site. The reason being that the Accelerator uses the name of the folder (under sites in your blob storage) as binding for the site, which is automatically generated on your Azure instances. This poses some limitations, which I created a workaround for.
In order to use the workaround you will have to add some code to the web role of the accelerator, which is explained here:
http://waacceleratorumbraco.codeplex.com/discussions/254223
Hope it helps
- Morten
Thank you for your answer Morten! We had to do some minor modifications to your solution due to different versions of accelerator, but your example was what we needed to get started.
is working on a reply...