New Installation
Submitted by ctsuhako on Wed, 09/26/2007 - 15:49.
Hello:
I am new to Project Pier and am trying to install on an Ubuntu system. I have installed to the directory /var/www/projectpier, but the environment checks are giving me the following errors:
# Error: /config/config.php is not writable
# Error: /public/files is not writable
# Error: /cache is not writable
# Error: /upload is not writable
The permissions are set for my user to Create and delete files in the entire folder. What other permissions do I need to change?
Thanks!
Hmmm, all my experience is with non-local shared hosts or with server packages like Mamp/Xampp.
However, I imagine that manually setting the given folders to 777 would allow it to install and run properly. There might be a more subtle way of doing it locally, but that's my brute-force solution (and the one i've always settled for with shared hosting)
Hi, Jeremy:
I chmod'ed the entire projectpier folder to 777 and still no joy. Thanks anyways.
please help...
somebody knows what to do?
usually the webserver runs under its own user account (not yours) when in linux, so try making the root folder 777 (and do it recursively so that all files/folders underneath it are also 777).
You can also try changing ownership of the files/folders to the webserver user account. Keep in mind that you will probably want to change the permissions back to something more secure once you are up and running, unless this is just a test/dev installation. Good Luck!
Although you changed the permissions on the projectpier folder I think they are not set on the needed files. Setting permissions is not a recursive operation by default.
So, to solve the problem simply go to the config.php file and set it's permissions to 777, do the same for the other folders and you should have it working. But please restore the original permissions on the projectpier folder and see if nothing else is world writable, you can have some security problems there.
I haven't checked if 777 is actually necessary, maybe a more restrict permission set can be applied.
Wow! I think I can actually help here. I just installed projectpier on a freshly installed ubuntu 6.10 server and had the same problem. Rather than granting all permissions to everyone (chmod -R 777) I choose to change ownership of the files and directories in question.
So first thing I needed to do was check what user apache2 was running as. In my /etc/apache2/apache2.conf file I could see it was running as user www-data and group www-data.
So I issued the following:
#chown -R www-data:www-data /var/projectpier
(where /var/projectpier/ is my install directory)
And this solved the problem. fyi... the permission on all these files were
wrxr-xr-x and the directory was drwxr-xr-x
Also with Ubuntu, you may need to use sudo to issue that command if you're not using root.
Yes - The post by davidl is correct. You should change ownership of the PP directory recursively to the apache user (www-data on Debian/Ubuntu systems). Don't chmod to 777 however - as this means that any user on the system will be able to modify files etc.
You want
chmod -R 755 /path/to/projectpier
chown -R www-data:www-data /path/to/projectpier
(or whatever the Apache user runs as on your system)
Regards,
Patrick