Before I click on the create server button i want to have everything setup first…
The sites that i want to use will be like what you can get from purchasing a shared hosting package.
apache webserver, email, webmail, php, cgi, mysql, ssl, ftp, spam … i think thats basically it
These servers will be used for php applications mostly like joomla, custom built, ajax, javascrpit development ect.
Can someone help me in what to select in
- allowed virtual server features
- allowed capabilities.
in features i am seening things like administration user, and home directory, which i dont quite understand what they are.
Is there a detailed doc somewhere on Account Plans that explains in detail what each option is?
The other thing is I assume server templates come in somewhere in this whole thing … what do I do with them.
People tend to modify those settings not because any are “bad”, but because they want to offer different “plans”, some costing more than others. Perhaps a low-cost plan wouldn’t include SSL, for example, but for a few more dollars a month they can upgrade to a plan that contains the SSL feature.
If you aren’t sure what exactly they are, or you don’t multiple kinds of “plans” that you hope to offer, you’re probably best off leaving each of those settings at “Automatic”.
Then later on, as you could play around with having multiple types of account plans at different costs.
You’re right, there should be documentation on that screen. In fact, not having it there is probably a bug (consider submitting a report using the Bugs and Issues link below so Jamie can add it
However, if you go into an existing Virtual Server, and select Administrative Options -> Edit Owner Limits -> Allowed capabilities and features, click "Edit capabilities for virtual servers" and "Allowed features for servers" to get a help document what those features do.
… about the Server Templates…I guess I don’t need to touch those then.
yes you do want to touch the server templates.
they are the very basis of your servers. like will you run in mod_php or mod_fcgid. that is a huge difference. Do you have slavenameservers, send an email with customised text etc. those go in the templates.
the plans you need for quotas on webspace, bandwidth, sub-servers, databases available features etc.
The plans have been extracted from the templates because there where many requests so hosters can upgrade/downgrade customers to other plans more easily (automated way)
The old way was to switch a client to another template but all the quotas had to be done manually. Now you can switch to another template (from mod_php to mod_fcgid) without changing quota’s and features.
Also now you can switch to another plan without the server being switched to a different execution mode.
It became much more flexible, but the initial set up needs to be done properly according to what you will sell.
I also suggest to create server templates (cloned from default) give them a name and give the plans the same name as the templates.
if in any later stage you want additional software to handle automatic provisioning this in my experience seems to come in handy.
Thats what I’m saying…I’m not selling …this is for private use for web app development and testing. So i just need to be able to create various size virtual servers that run along the lines of what a regular shared hosting plan would be.
So from what you are saying since my needs are simplistic for now I s’pose i don’t need to touch it without further reading up on it.
But can’t wait for that i am itching to create this first VS.
Fantastic idea. Didn’t even think about that. Thanks for that.