Skip to content
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

[BUG] Build now fails due to sites/default being unwritable #399

Open
alxp opened this issue Jun 24, 2024 · 2 comments
Open

[BUG] Build now fails due to sites/default being unwritable #399

alxp opened this issue Jun 24, 2024 · 2 comments

Comments

@alxp
Copy link
Contributor

alxp commented Jun 24, 2024

Noticed a build failure when I pushed a commit to an open ISLE-DC PR this evening. Log is here.

Notice: ] Performed install task: install_select_profile
Notice: ] Performed install task: install_load_profile

In install.core.inc line 2329:
																			   
  Settings file:The <em class="placeholder">Settings file</em> is not writabl  
  e.<br /><br />The Drupal installer requires write permissions to <em class=  
  "placeholder">./sites/default/settings.php</em> during the installation pro  
  cess. The <a href="https://www.drupal.org/server-permissions">webhosting is  
  sues</a> documentation section offers help on this and other topics.         
																			   

make[1]: *** [Makefile:580: starter-finalize] Error 1
make[1]: Leaving directory '/home/runner/work/isle-dc/isle-dc'
make: *** [Makefile:159: starter] Error 2
Error: Process completed with exit code 2.
0s
0s
0s
0s
0s
0s
0s
1s

```shell

I know we've dealt with similar issues in the past, is it a matter of doing another chmod / chown?
@joshdentremont
Copy link
Contributor

joshdentremont commented Jun 26, 2024

This might be the same issue here: #306

We talked about chown in the tech call, but in my testing, the owner didn't have permission to write to settings.php, so I think we would need to also give the owner write permissions.

@adam-vessey
Copy link
Contributor

Something such as Drupal's $settings['skip_permissions_hardening'] setting might be useful; though, would only expect it to be used in dev environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants