Hello there, I’m starting a new project and want to know if I’m in the right way! 

- I have to do 17 websites (for 17 events).

- Each website will have maximum 20 pages. 

- I want to install 1 Dotnetnuke website and create 17 different parent portals in it.

- Each of these portals will have more than 5 domain names redirecting on it. 

I will be in charge of maintaining those websites, so my customers won’t be able to access the code, but they will be able to add/update content.

 
So here are my questions:

 
1) I found this paper about NOT use multiple portals on DNN:

http://powerdnn.com/Resources/Whitepapers/DotNetNukeforVerticalSolutionProviders/tabid/166/Default.aspx

- What do you think about this issue?

- Do you think having 17 websites with 20 pages each on the same DNN will decrease performance and speed?

 
2) How can I do to redirect each domain name to their related portal… is it only in the portalAlias table of the database?

Example: a.com, aa.com, aaa.com all must redirect to portal #1

So each of these domain names will have a row in the portalAlias table with #1 as portalID…

3) Do you know a nice Hosting provider where I could host this project for less than 200$ / year?

1. I read that page a long time back.. it's pure fud written to support their hosting offer.
   17 portals of 20 pages on a single instance is exactly the same as 340 pages in a single portal.
   In fact, having 17 portals in one instance saves massiveley on resources and with a limited budget, that equates to performance. one times 150Mb versus 17 times 150mb of ram.. work it out.
   
   The rule: You have to have perfect procedures when working with DNN. Backing up, restoring, testing etc. If you have commercial client then these things must be tight.
2. Yes, just the portal alias table
3. The limited hosting budget is the weak spot in the plan. I can't see how $200 for a whole year relates to the cost in time and effort put into 17 portals for 20 events run by how many dozens of people for how big an audience?.... Good hosting is the backbone of the whole thing.. you simply have to buy the resources that are required.  Placing a limit like that on it is a problem right from the get-go.
   
   An alternative might be to go for a free or cheap hosted service like Google Sites.

Rob

Hey guys!

Thanks for your answers!

I finally got more budget for my hosting... (we are a non-profit organization... so it's why I don't have a lot of money).

But I was looking for some hosting providers, and they seem to be cheap and provide me all what I want (unlimited domain name pointing to my DNN, enought mssql space, enough bandwith and hd space) What do you think about them: (speed, uptime, performance, etc.) ?

- Webhost4life.com (120$ / year)
- Powerdnn.com (240$ / year)
- iHost.com (170$ / year)
- dotnetpark.com (150$ / year)

And for your question Mitch, NO I will not have to separate my websites laters. All events will be in different time of the next year, so I will have different trafic peak for each of them, but for sure, not for all of them at the same time.

Those event websites will die maximum 6 months after the events. Only 3 venues websites will stay active and will be updated by the venue managers after. So I'm not sure if I will separate the Venue websites from the Sport Events websites...(in 2 DNN installations). Maybe yes, because when the Sport Events website will no longer exist, they will still be in the database and I'm not sure somebody will know how to clean it...!!!