-
|
I've got my Now suppose there's a few additional How would you approach this? Is there a way in eleventy to include specific, arbitrary files as part of the 'input'? Or would you set up a build step in package.json that copies those specific files over first before eleventy runs? Something else? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
If the "../../common/123.md" file is outside of the input folder, I've seen some people use symlinks in the past. |
Beta Was this translation helpful? Give feedback.
-
|
Hey thanks for the answer. The approach I ended up going with, was via docker-compose, volume mounts. version: "3"
services:
eleventy:
image: node:16-slim
volumes:
- ${PWD}:/app
- ${PWD}/../common:/app/common
- ${PWD}/../../specific.md:/app/text/specific.md
working_dir: /app
environment:
- DEBUG=Eleventy*
command:
- /bin/sh
- -c
- |
npm install
npx eleventy --watch --serve
ports:
- 8080:8080
It does work, the --watch and --serve is doing fine, but does have some minor quirks I can live with. Namely - Ctrl + C takes a while to 'kill' the application, it's fine. |
Beta Was this translation helpful? Give feedback.
Hey thanks for the answer. The approach I ended up going with, was via docker-compose, volume mounts.
It does work, the --watch and --serve is doing fine, but does have some minor quirks I can live with. Namely - Ctrl + C takes a while to 'kill' the application, it's fine.