Skip to content

feat: give fresh Drupal projects a default database - #95

Merged
geodro merged 1 commit into
mainfrom
feat/drupal-default-service
Sep 30, 2026
Merged

geodro merged 1 commit into
mainfrom
feat/drupal-default-service

Conversation

@geodro

@geodro geodro commented Sep 30, 2026

Copy link
Copy Markdown
Member

A fresh Drupal project has no database settings yet, so there is nothing for lerd to detect, and lerd setup --all could not finish on one. The four Drupal definitions now name mysql through the new optional env.default_service key, so a new project gets it wired up while an existing site on PostgreSQL or SQLite keeps the database it already uses. Binaries that predate the key ignore it and behave exactly as they do today.

Refs lerd-env/lerd#2057

A recommended-project scaffold names no database driver until the Drupal installer runs, so lerd env found nothing to wire and lerd setup --all could not finish on a new project.

Each Drupal definition now sets env.default_service to mysql, which lerd uses only when the project names no database at all, so a site already on PostgreSQL or SQLite keeps its driver. Older binaries do not know the key and ignore it.
@geodro
geodro requested a review from a team as a code owner September 30, 2026 09:49
@geodro
geodro merged commit 1f3ac6e into main Sep 30, 2026
1 check passed
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

Successfully merging this pull request may close these issues.

1 participant