If I buy an Intel 512MB Ram 2-40 GB HD dedicated plesk server, is the PSA that is already installed a Standard installation or RPM installation? (im getting my new manual together and learning all about this since ciho(cough) suddenly charged me $31,000 more than my usually $250/month for a bunch of accounts I never heard of bringing an end to one web hosting company and possibly my credit rating for the next 14 years since I did sign their payment policy and I'm not/can't pay for their made up charges.)
...sorry. rackshack lists paths for both Standard Installations and RPM Installations and I don't know which one I will end up with. if I can choose what is y`alls opinions on which is best?
Anybody got a list of Paths to programs and their Versions as what was setup on your plesk server like, Perl 5.0053, Java, Sendmail, python 1.5, pgp 6.5, date, c++, whois? I'll check later but was wondering.
Possible Shared SSL Solution
Don't know if this will work but I am going to put the URLs im my manual for now:
It is possible to enable the Apache UserDir directive in the Apache configuration file. This will allow all domains on the server to be accessed via a web browser at http://www.maindomain.com/~domainonserver
I could then buy a certificate for the IP based www.mymaindomain.com site.
Then I "think" all site's web pages on that server could be accessed at https://www.mymaindomain.com/~domainonserve...ver/anypage.htm (maybe it don't work with https? what about cgi's and php?)
This would eliminate the need to create a Domain User account for ssl pages every time you setup a new domain on the server that needs to use SSL.
This would also eliminate the need for your Hosting customer to have to upload their secure pages using a separate ftp account, because www.mymaindomain.com/~domainonserver/ will automatically show the contents located in that domains vhost directory.
This would also allow you to give a URL to the Hosting customer that they could use to view their site before domain propagation!
===
The only solution to a Shared SSL certificate for use by all domains on the server that I have found here so far is this:
Secure your main ip based site -> www.mymaindomain.com
Add a Domain User for the customer to the domain mymaindomain.com through PSA. -> www.mymaindomain.com/~hostingcustomer
Hosting Customer then uploads files to the server that will be stored in the www.mymaindomain.com/customer/ directory.
So, the customer has to juggle to ftp accounts, one to upload his main site and the other to upload pages to the secure server.
===