Hi,

If you implement something like this you should implement it as separate projects, it does not need to be included in mojoPortal nor does it require changes in mojoPortal to implement such a feature.

I have listed on my Road Map that I actually plan to implement a feature like  this named Site Provision Pro, that will enable ad hoc site provisioning with an option to use ecommerce to charge before a site can be provisioned. This will be a paid add on feature when I implement it but nothing stops a developer from implementing something similar.

Best,

Joe

Hi,

First thanks for the coffees!

I'm afraid the bad news is that the feature is only in the planning stage, I don't have a target date for it yet.

Best,

Joe

Hi Soven,

A lot of what you describe is very project specific, client lists etc. We currently support 2 scenarios, one where sites are completely independent and have different users and roles, and then we have related sites mode where all sites share the same users and roles.

I think in your scenario you could implement some logic to synchronize users and roles across client specific sites. You can keep all extra data in your own tables linked by SiteID or SiteGuid.

Note that things are quite different depending on whether using folder based child sites or host name based sites. One of the challenges of host named based sites is creating the needed DNS records on demand. My planned feature will work out of the box with folder based sites but for host name based sites it will expose events where its possible to hook in other supporting functions so that host names could be provisioned by some external web service.

Do as much as you can to keep your code in your own projects, if you bump into things that make you think you need to modify mojoPortal code then post specific questions and maybe I can recommend a strategy that requires no changes to mojoPortal code or maybe I will consider small changes that make it easier to support your needs. Its a case by case judgement.

I noticed that you are in NC, I'm in Charlotte myself.

Best,

Joe

Hi,

Well the problem is that generally host name DNS records can take up to 24 hours to propagate across the internet. I use Yahoo Domains and generally when I create a new host A record its working for me within about 30 minutes but may not be working around the world that fast. Some DNS services can promise much faster propagation but they are usually pretty expensive.

The way I see it, unless you can automate the DNS provisioning and make it nearly real time the site provisioning feature does not really express its potential. I mean if a real person has to manually create the DNS record to provision a site then you might as well just use an existing feature like a contact form or Form Wizard Pro, to capture the request for a site and then manually create the site from the site settings in the root admin site right after setting up the DNS. Its only a few clicks to create a new site.

Best,

Joe