Skip to content

Commit bf8e6d5

Browse files
authored
Add documentation for feature in plone#92
https://github.com/plone/plone-backend/pull/92/files related.
1 parent e184d6c commit bf8e6d5

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

docs/install/containers/images/backend.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,13 @@ Plone 6 example:
6565
docker run -p 8081:8081 -e LISTEN_PORT=8081 plone/plone-backend:{PLONE_BACKEND_VERSION}
6666
```
6767

68+
#### Adding configuration to `zope.conf`
69+
70+
It is not possible to add configuration fragments to `zope.conf` directly, like
71+
it is with the `buildout` deployment method. However, you can derive your own
72+
container image, and drop in configuration fragments. See *Extending from this
73+
image* below for instructions.
74+
6875
### Site creation variables
6976

7077
| Environment variable | Description |
@@ -304,6 +311,19 @@ And start a container.
304311
docker run -p 8080:8080 myproject:latest start
305312
```
306313

314+
### Adding `zope.conf` configuration fragments
315+
316+
In the directory containing your `Dockerfile`, create a folder `etc/zope.conf.d`.
317+
Add your `zope.conf` configuration fragments there.
318+
319+
Now add the following to your `Dockerfile`:
320+
321+
```Dockerfile
322+
COPY /etc/zope.conf.d/*.conf /app/etc/zope.conf.d/
323+
```
324+
325+
This ensures your fragments are deployed in the `zope.conf.d` folder, which then
326+
will be used to amend the `zope.conf` file prior to starting Plone.
307327

308328
## Advanced usage
309329

0 commit comments

Comments
 (0)