Jul
29
Written by:
jerryharbin
7/29/2010 3:19 AM
There are more and more hosting companies now offering DotNetNuke hosting from shared or virtual dedicated accounts, to dedicated or cloud hosting. Although hosting costs might be high for some businesses, shared hosting is sufficient enough to allow your site to have a simple online presence with low traffic handling. .
There are downsides of running shared hosting, but you don't have to worry much unless your Web site experiences a spike in traffic. I use GoDaddy shared hosting. One of the downsides of GoDaddy for DotNetNuke is that it won't allow you to have complete control of your URL. It adds an extension at the end proceeded by a slash (i.e. http://mydomain.com/something) for every domain you create.
To overcome this issue, here are the steps needed to change from http://mydomain.com/something to a legitimate http://mydomain.com in GoDaddy.
- Click on ‘Manage Account’ in the Web hosting page
- Click on 'Your Files' at the top.
- Check that the Root and DNN directories have the same permissions
- Backup both your DNN Web installation and your database
- Place html file called app_offline.htm into the DNN directory, taking the site offline
- Update the database table containing the Portal Alias from http://mydomain.com/dnn to simply http://mydomain.com
- Move the contents of the current DNN folder into the root
- Update any references you might have in your web.config file to your old site path.
- Remove the app_offline.htm file
Good luck!