Thread

Hi,
I’ve searched around, but can’t find any summary on installing EE (and the config.php file) outside of the webroot.

I’ve tried uploading the system files to “/var/www/a-safe-place/” and pointing the $system_path in “/var/www/html/path.php” to the safe place. No go.

Before I spend more hours trying to accomplish this, I thought I’d ask if it is accomplishable…

So, if someone could point me in the general direction, I’d appreciate it.

Thanks,
Matt

Let’s take a step back here, what exactly are you trying to accomplish? You can certainly install EE in any directory on your webserver, and then access it there. Are you trying to install it in one place, and then access it via a different URL, pointing to some other directory? I would try to avoid that, if possible.

Which version and build of EE are you on, by the way? Moving to “Installations”.

OK, backing up….

My main goal is to have the installation be as secure as possible, while still keeping the upgrading process easy - and the number one concern is probably having the config file outside of the webroot.

The previous server setup I inherited has had major (non-EE related) security/hacking problems, so I’m trying to keep things under control as I move to a new server.

P.S. I already have CodeIgniter running smoothly on the new machine.

Thanks.

My main goal is to have the installation be as secure as possible, while still keeping the upgrading process easy - and the number one concern is probably having the config file outside of the webroot.

I am note sure this is feasible. EE expects config.php in the system directory, which needs to be below the webroot. To be honest, I don’t quite see the point: Rename your “system” directory to something unguessable, and you should be fine. Even if you bring up config.php in your webbrwoser, you’ll only get “Invalid file request”.

The previous server setup I inherited has had major (non-EE related) security/hacking problems, so I’m trying to keep things under control as I move to a new server.

EE was built with security in mind. It’s an issue we take very seriously indeed.

Thanks, Ingmar.
I’ll just do it the usual way.

matt

While I won’t swear it can’t be done- I think going stock (and renaming the system folder) is definitely the way to go on this one.  And if you run into any more issues, just open up a new thread and we’ll take a look.