Skip to content

Explain generated files and Drupal settings in workspaces - #128

Draft
csandanov wants to merge 1 commit into
masterfrom
docs/workspace-generated-files
Draft

csandanov wants to merge 1 commit into
masterfrom
docs/workspace-generated-files

Conversation

@csandanov

Copy link
Copy Markdown
Member

Workspaces are changing in two ways that customers will notice, and this updates the workspaces page to match:

  • Git status: files the service generates, such as installed dependencies or Drupal core and contrib modules, no longer show up. Setup lists them in the checkout's .git/info/exclude, so the project's .gitignore doesn't change, and custom code still shows.
  • Drupal settings: setup now creates settings.php or adds Wodby's settings include to it, instead of stopping when the file is tracked in Git. The include loads only when Wodby's settings file exists, so it's safe to commit.

Validation

  • mkdocs build --strict in the wodby/mkdocs image.
  • test_agent_docs.py and check_agent_contract.py: pass.

Merge order

Keep this as a draft until the behavior is live: the Drupal image release from wodby/drupal-php#115 and the service updates in wodby/service-drupal-php#11, wodby/service-php#8, wodby/service-node#5, wodby/service-nextjs#5 and wodby/service-python#7.

Workspace Git status now leaves out files the service generates, such
as dependencies and Drupal core, through the checkout's
.git/info/exclude. Drupal setup creates settings.php or adds Wodby's
settings include, which loads only when Wodby's settings file exists,
instead of refusing to change a tracked settings file.
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