For reference, here's how we go things working. These are just a rough guide, and relate to Plesk:
- Get a working copy of git (or ask someone to install it)
- In the website settings, change the PHP application setting to use FastCGI.
- Apache runs as the 'apache' user
- FastCGI runs as your user
- SSH to the server
- You need to set this up - google for how to do this for your version of Plesk
- Upon login, you'll be in /var/www/vhosts/<domain>
- mkdir private/moodledata
- cd into httpdocs (or httpsdocs if you want SSL)
- Clone the repository:
- If you want it in the root directory: git clone git://git.moodle.org/moodle.git . (yes - that dot is important. It means current directory)
- If you want Moodle in a subdirectory, specify this instead of the . (git clone git://git.moodle.org/moodle.git foo)
- Run your setup
- During setup, you'll be asked for the path to your moodledata. You'll need to use /var/www/<domain>/private/moodledata (or whatever you called it). Moodle makes an effort to fill this in, but the directory it suggests isn't writeable by the web server so you need to use a different directory instead.
These instructions are only a rough guide and may not be 100% relevant to your version of Plesk.
I know it's possible to have Plesk running Moodle using Apache rather than FastCGI, but for a hosting solution I think it's probably easier if all of your data is owned by your own user. It also means that the new plugin installer in 2.5 will just work without any chmod/chown.