VPS is not the way to go IMHO. It's expensive, and takes much more time managing.
I haven't installed joomla on the VPS yet. Will do do in the next few days and report back. but basically.... if there were ownership issues it would be in my power to change the ownership... On my VPS, i'm the boss . This is great if you're familiar with linux and shell commands. Maybe this is even configurable in Cpanel/WHM but I haven't had to explore this though.
I hadn't used linux for 5yrs at least, so have had to spend quite a bit of time on forums reading tutorials
I think the ownership issue is fixed by some foreign animal called phpsuexec. When you sign up for a VPS with servint you get to configure what's installed on your machine. I seem to recall that phpsuexec was an option that i had to pay for.. can't even remember whether I chose it or not.
Basically unless you're prepared to go through a steep learning curve, go the reseller option with rochen or elsewhere. VPS is a pain in the butt for noobs. All my joomla sites still run off my reseller account at an australian host.
I chose it for three reasons.
1.) I am setting up a site that will eventually require a dedicated server (running phpfox) so this was the logical step in that direction.
2.) I've always wanted to do this. I just think it's cool to have a server somewhere on the other end of the earth that i can control remotely. I can turn it on and off at will. I can do whatever I want with it.
3.) I wanted complete branding of my services. With a VPS I run my own nameserver so i have my domain as domain.com and nameservers as ns1.domain.com and ns2.domain.com. Also, when my clients receive my emails, the header info in the emails shows blah.domain.com as the hostname.
Servint has a great forum by the way. Support has also been top notch so far.
EDIT:
I found this:What is PhpSuExec, and how will it affect my site?
PHPSuExec does for PHP Scripts what SuExec does for Perl files.
That is, it makes them run under your specific user account, as opposed to the Apache user account. This allows us to better monitor the resource usage of accounts, as well as track down runaway script files with greater ease. For you this gives you the benefit of all your php scripts running 'in' your account. For some PHP applications, such as PHPWebSite, this is a great help, as now when you create files/folders from inside the script, they will be owned properly by your account, and not the generic Apache user account.
The implementation of PHPSuExec does add a restriction or two to the use of PHP Scripts... these mainly being:
- You need to call the php file directly, you can't symlink to it and use that symlink as the url.
- PHP Scripts should have their permissions set to 0400 (owner read) or 0600 (owner read/write), and should be owned by your account. If you accidently set a file as world or group writeable, the phpsuexec module will not allow the script to run.
- A PHP file cannot be execute in a directory that is group-writtable or world-writtable.
from:
faqs.purenrg.com/fom-serve/cache/63.html