New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
attempt to create the directory ../config/sync failed, possibly due to a permissions problem. #274
Comments
I've got the same problem and same solution worked for me. |
Could you provide some information about the environment you are using? |
I'm running with macports on macOS Sierra 10.12.4 Composer version 1.4.1 2017-03-10 09:29:45 Here are the PHP extensions I have installed:
Here's the output given when running:
|
@webflo same issue than #274 (comment) I have manually created ../config/sync directories but when I try to access to site after installation ends it results in a "File not found" blank page. Then checking directories and files owner I see that all of them have my user as user and group (no "www-data" group), all files permissions are 0644 and all directories are 0755. To test if It was a permissions/owner issue I have changed everything too less restrictive option (0777 and user:www-data) but error "File not found" continue. Nginx error log says: 2017/06/25 19:15:47 [error] 9160#0: *627 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: xx.xx.xx.xxx, server: xxx, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "xxx Command used for installing : composer create-project drupal-composer/drupal-project:8.x-dev test --stability dev --no-interaction Enviroment: |
Sorry previous Nginx error commented in #274 (comment) was not related with ../config/sync. If It helps someone solution It's explained in 2.
After manually create config and sync directories, drupal "report status" warnings about ../config/sync folder was not writeable and in "Recent log messages" warnings about "Couldn't write .htaccess file. Please create a .htaccess file in your ../config/sync directory [...]" so I changed ../config permisions to 775 (644 before) and owner and group to [myuser]:www-data ([myuser]:[myuser] before). Not sure if it's is the best option but none combination of 755/775 with [myuser]/[www-data] works for me except this.
I set correctly the corresponding nginx directive for the site.
Trying to find the solution I changed more params in fastCGI_params section of nginx directive and in other related files like etc/php5/fpm/pool.d/example.conf, although It seems not be related to the config/sync error solution. |
Explanation and solution here https://drupal.stackexchange.com/a/233459/55010 |
Hi @webflo would It be possible to add the recommended and needed permission setting to the readme.md? Would be very helpful for people and for you, dealing with all that issues. |
To all with permission erros. Please follow this guide and never symlink your home/project-dir! |
In your settings.php file :
More information here |
Interesting - this is still a problem today. Very annoying. My PR 415 didn't get much response. |
This pull request/issue has been inactive for over a year and is being closed due to inactivity. If the issue still persists or the contribution is still relevant, please feel free to reopen it or create a new one. Thank you for your understanding and your contributions to the project! |
Doing an initial install by running
composer create-project drupal-composer/drupal-project ~/Sites/drupal8-composer --no-interaction --stability dev
as suggested from the README.md I got the following error on Drupal's install screen:I think this might related to #86 but it seems here that the config directory set in settings.php has already been moved out of the web root. Creating the
config/sync
directory in the composer root without changing settings.php resolves the issue for me. Should the process create this directory appropriately so a site install can happen immediately after running create-project?The text was updated successfully, but these errors were encountered: