openpublic + project mapper app = "...web server needs write access..."

I'm having the same issue. I thought maybe I needed to chmod 777 profiles/openpublic/modules just in case, then that didn't help.

(I'm running on localhost MAMP for the record.)

bump, same issue.

I got this working by recursively allowing write access to the sites directory and everything within it.

For example my setup is nginx + php-fpm
The owner of the sites directory and everyhing below is my web server's user nginx and the group is the PHP processes user, in my case php-fpm.
I set this with 'chown -R nginx:php-fpm sites/'
You can then give write write access to the web server and PHP by using 'chmod -R 775 sites/'

I could then install the project mapper app.

You could test this out, albeit unsecurley, by recursively giving everyone write access to the site directory and everything below with 'chmod -R 777 sites/'

Hope this helps - now to figure out if I can get UK maps in the Project Mapper app.

How do you install OpenPublic on BlueHost?

"chmod -R a+w sites " works for me. Of course, remember to change it back to "775" after the installation.

For Aegir users I did "chmod -R 777 sites", ran the app installs from within OpenPublic and then did an Aegir "verifiy" to reset all the files permission. Final did a "drush cc all" and everything worked.

P.S> We do not have FTP installed on this server.

Temporarily chmod'n everything to 777 does not work for my Aegir environment.

I added my www-data user (apache user) to the admin group and gave that group write permissions to all of sites, but it's not working. I can't think of any reason why that wouldn't ordinarily work. Need some help from the OpenPublic folks here to debug that. Seems like the installer needs more access than it describes and of course there is no documentation about it. :-/

So short answer is that web server needs write access to sites/, that is all. Not just sites/all but sites/ too. Not perfect, but we are working on some alternatives. Truth be told it is just integrating with the core Updater that you might use if you uploaded a tar.gz so it's not like we wrote anything special for that. Aegir installs I guess are slightly tricker, but #6 works and the good thing is if you have one OPic platform you really only need to "install" an app once and it will be there for all future sites setup using that platform without creating modules dirs etc.

Going to leave it open b/c we need some better alternatives. Erik, assigning to you to keep it on your radar.

Tracking. Giving write access for httpd in /sites doesn't make me feel good.

This is really an openpublic issue and not an app one?

This problem may be due to the fact that the owner of the directory and httpd - not the same?
E.g., when you run a local - httpd as root.

If you use an manged Aegir service, you will not have access to set the site/ permissions as suggested by #6. A user only gets write access to site/site-name/

What about installing Apps to an individual Aegir site via a drush command?

There is patch for Aegir which does all the required magic: http://drupal.org/node/1088472#comment-5819896

This seems "fixed" based on above comments