Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
Documentation
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Monitor
Service Desk
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
DevOps Tools
Documentation
Commits
577d050f
Commit
577d050f
authored
4 years ago
by
jurgenhaas
Browse files
Options
Downloads
Patches
Plain Diff
Add a small section to describe relationship between L3D and Drupal development
parent
6a7399b7
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#33657
passed
4 years ago
Stage: build
Stage: deploy
Changes
2
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/docker/l3d/drupal.md
+49
-0
49 additions, 0 deletions
docs/docker/l3d/drupal.md
mkdocs.yml
+1
-0
1 addition, 0 deletions
mkdocs.yml
with
50 additions
and
0 deletions
docs/docker/l3d/drupal.md
0 → 100644
+
49
−
0
View file @
577d050f
---
title
:
Docker L3D and Drupal Projects
tags
:
-
docker
---
# L3D and Drupal Projects
We do provide a couple of project templates for Drupal projects out of the box:
-
[
Drupal 8
](
/composer/project/d8/
)
-
[
Drupal 9
](
/composer/project/d9/
)
If you prefer to use your own prroject template, you'll get the most out of
L3D if you add our ccomposer plugin
[
drupal-development-environment
](
/composer/plugin/drupal-dev-environment/
)
to your required dev components:
```
bash
composer require-dev lakedrops/drupal-development-environment
```
This comes with all the dependencies, that help you in local Drupal development:
-
[
Ahoy
](
/composer/plugin/ahoy/
)
-
[
Behat
](
/composer/plugin/b4d/
)
-
[
Docker4Drupal
](
/composer/plugin/d4d/
)
-
[
Dorgflow
](
/composer/plugin/dorgflow/
)
-
[
Drupal Environment
](
/composer/plugin/drupal-environment/
)
-
[
Traefik
](
/composer/library/traefik/
)
-
[
Utilities
](
/composer/library/composer-json-utils/
)
You'll find the documentation for each of these tools in their own section.
In the current context, just an extra note on the drupal-environment plugin: this
has been moved out of drupal-development-environment and contains all the tasks
and templates to initially build the directory structure and setting files.
It is a great idea to utilize the same structure in your production environment
too. To get there, you can simply add this plugin to your regular requirements:
```
bash
composer require lakedrops/drupal-environment
```
In both cases, development and production, your project settings for this
toolset goes into the file
`.lakedrops.yml`
in your project root and each
project describes in its own documentation, what values go into this file so
that you get similar (but not identical) setup on all stages. It should not
be identical, because you don't want all the development tools on your
production site.
This diff is collapsed.
Click to expand it.
mkdocs.yml
+
1
−
0
View file @
577d050f
...
...
@@ -36,6 +36,7 @@ nav:
-
Changelog
:
docker/gitlab-drupal-ci/changelog.md
-
L3D
:
-
Home
:
docker/l3d/index.md
-
Drupal
:
docker/l3d/drupal.md
-
Changelog
:
docker/l3d/changelog.md
-
Maven
:
docker/maven-build/index.md
-
Node
:
docker/node/index.md
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment