Skip to content

Commit 4e7507e

Browse files
rimi-itkrimi-itk
committed
Cleaned up Markdown
1 parent 042a574 commit 4e7507e

File tree

8 files changed

+39
-16
lines changed

8 files changed

+39
-16
lines changed

‎Taskfile.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,12 +31,14 @@ tasks:
3131
lint:markdown:
3232
desc: "Lint Markdown"
3333
cmds:
34-
- '[[ -n "$SKIP_FIX" ]] || docker run --rm --volume "$PWD":/md itkdev/markdownlint markdownlint {{.GLOB}} --fix'
35-
- docker run --rm --volume "$PWD":/md itkdev/markdownlint markdownlint {{.GLOB}}
34+
- '[[ -n "$SKIP_FIX" ]] || {{.MARKDOWNLINT_COMMAND}} --fix'
35+
- '{{.MARKDOWNLINT_COMMAND}}'
3636
vars:
3737
# We use a block scalar (https://yaml-multiline.info/#block-scalars) here to make escaping (a little) easier.
3838
GLOB: >-
3939
{{.CLI_ARGS | default "'**/*.md'"}}
40+
MARKDOWNLINT_COMMAND: >-
41+
docker run --rm --volume "$PWD":/md itkdev/markdownlint markdownlint --dot {{.GLOB}}
4042
4143
lint:shell-script:
4244
desc: "Lint shell scripts"

‎templates/drupal-10/.docker/data/README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,13 @@
22

33
Please map persistent volumes to this directory on the servers.
44

5-
If a container needs to persist data between restarts you can map the relevant files in the container to ``docker/data/<container-name>`.
5+
If a container needs to persist data between restarts you can map the relevant files in the container to
6+
`docker/data/<container-name>`.
67

78
## RabbitMQ example
8-
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for RabbitMQs data directory to avoid losing message on container restarts.
9+
10+
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for
11+
RabbitMQs data directory to avoid losing message on container restarts.
912

1013
```yaml
1114
# docker-compose.server.override.yml

‎templates/drupal-7/.docker/data/README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,13 @@
22

33
Please map persistent volumes to this directory on the servers.
44

5-
If a container needs to persist data between restarts you can map the relevant files in the container to ``docker/data/<container-name>`.
5+
If a container needs to persist data between restarts you can map the relevant files in the container to
6+
`docker/data/<container-name>`.
67

78
## RabbitMQ example
8-
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for RabbitMQs data directory to avoid losing message on container restarts.
9+
10+
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for
11+
RabbitMQs data directory to avoid losing message on container restarts.
912

1013
```yaml
1114
# docker-compose.server.override.yml

‎templates/drupal-8/.docker/data/README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,13 @@
22

33
Please map persistent volumes to this directory on the servers.
44

5-
If a container needs to persist data between restarts you can map the relevant files in the container to ``docker/data/<container-name>`.
5+
If a container needs to persist data between restarts you can map the relevant files in the container to
6+
`docker/data/<container-name>`.
67

78
## RabbitMQ example
8-
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for RabbitMQs data directory to avoid losing message on container restarts.
9+
10+
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for
11+
RabbitMQs data directory to avoid losing message on container restarts.
912

1013
```yaml
1114
# docker-compose.server.override.yml

‎templates/drupal-9/.docker/data/README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,13 @@
22

33
Please map persistent volumes to this directory on the servers.
44

5-
If a container needs to persist data between restarts you can map the relevant files in the container to ``docker/data/<container-name>`.
5+
If a container needs to persist data between restarts you can map the relevant files in the container to
6+
`docker/data/<container-name>`.
67

78
## RabbitMQ example
8-
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for RabbitMQs data directory to avoid losing message on container restarts.
9+
10+
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for
11+
RabbitMQs data directory to avoid losing message on container restarts.
912

1013
```yaml
1114
# docker-compose.server.override.yml

‎templates/symfony-3/.docker/data/README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,13 @@
22

33
Please map persistent volumes to this directory on the servers.
44

5-
If a container needs to persist data between restarts you can map the relevant files in the container to ``docker/data/<container-name>`.
5+
If a container needs to persist data between restarts you can map the relevant files in the container to
6+
`docker/data/<container-name>`.
67

78
## RabbitMQ example
8-
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for RabbitMQs data directory to avoid losing message on container restarts.
9+
10+
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for
11+
RabbitMQs data directory to avoid losing message on container restarts.
912

1013
```yaml
1114
# docker-compose.server.override.yml

‎templates/symfony-4/.docker/data/README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,13 @@
22

33
Please map persistent volumes to this directory on the servers.
44

5-
If a container needs to persist data between restarts you can map the relevant files in the container to ``docker/data/<container-name>`.
5+
If a container needs to persist data between restarts you can map the relevant files in the container to
6+
`docker/data/<container-name>`.
67

78
## RabbitMQ example
8-
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for RabbitMQs data directory to avoid losing message on container restarts.
9+
10+
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for
11+
RabbitMQs data directory to avoid losing message on container restarts.
912

1013
```yaml
1114
# docker-compose.server.override.yml

‎templates/symfony-6/.docker/data/README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,13 @@
22

33
Please map persistent volumes to this directory on the servers.
44

5-
If a container needs to persist data between restarts you can map the relevant files in the container to ``docker/data/<container-name>`.
5+
If a container needs to persist data between restarts you can map the relevant files in the container to
6+
`docker/data/<container-name>`.
67

78
## RabbitMQ example
8-
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for RabbitMQs data directory to avoid losing message on container restarts.
9+
10+
If you are using RabbitMQ running in a container as a message broker you need to configure a persistent volume for
11+
RabbitMQs data directory to avoid losing message on container restarts.
912

1013
```yaml
1114
# docker-compose.server.override.yml

0 commit comments

Comments
 (0)