We are on Rackspace Managed Cloud Servers. We have vhosts set up. My folder structure looks like this: -/var/www/vhosts/mysite.com If this what you expect? could I just put the admin files in "www"?
My setup is the same. I configure my vhosts with the following:
- Public is where the vhost actually points to to serve up the website.
- Log is where log files are stored.
- Database is a folder I create to store mysql dump files to move copies of my db around.
- System is the EE system directory, one level up from
Once you change your
admin.php to use
../ syntax to look 1 directory up, it should all work.
We also use Focus Lab's Master Config approach.
Within public, I create a
ee directory that contains
third_party. This is where I manage third party add-ons and my config.php within the
I also store
templates in the public directory, nested within another directory containing our front-end assets (images, css, js). This lets us point CodeKit at 1 directory instead of having it monitor the whole application.
If you're accessing the server via SSH/command line, your vhost configurations are typically in a location such as
/etc/apache2/sites-available (on Ubuntu). If you edit that file, you'll see that you can point the website to the public directory. I'm assuming this is what they're referring to when they say "redirect to this nested folder."
A few years back I printed out a set of Slicehost's articles and put them in a binder. I use those every time I set up a new Ubuntu server, from SSH accounts to firewall to Apache/PHP/MySQL and vhost config. You can start here or jump right to vhosts config.