Avoid absolute paths in settings.php

Created on 19 April 2025, 6 days ago

Problem/Motivation

Drupal Flake adds a stanza to the settings.php file to include its database settings. This include uses the hardcoded current path on the system -- which makes it not portable.

It does rewrite this at startup, but if you have multiple developers that keep their local copies in different paths, you end up with changes to the settings file -- if this is tracked in git (which I recommend) then this is not ideal.

Steps to reproduce

Set up a site with Drupal Flake, start the services, and commit the settings file.

Move to a different machine or different directory, and start the services again. You now have an override on the settings.php file which you have to deal with -- ignore, commit, etc. If you commit and push, you could cause merge conflicts for other developers.

Proposed resolution

Make sure the paths in the Nix Settings block are all relative to the $app_root.

✨ Feature request

Status

Active

Version

1.0

Component

Code

Created by

🇺🇸United States freelock Seattle

Live updates comments and jobs are added and updated live.

Merge Requests

!1Avoid absolute paths in settings.php
Merged
🇺🇸United States freelock
updated 6 days ago

Comments & Activities

Issue created by @freelock
Merge request !11.0.x → (Merged) created by freelock
Comment 6 days ago →
System Message

freelock → committed 8617d1bb on 1.0.x
Issue #3520079 by freelock: Avoid absolute paths in settings.php
Comment about 15 hours ago →
System Message

freelock → committed 32a807e1 on 1.0.x
Issue #3520079: Avoid absolute paths in settings.php
Comment about 12 hours ago →
🇺🇸United States freelock Seattle
Additional fix - some missing characters in newly generated settings blocks.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024