2 ms·
It's not like you have to maintain a fork, it's pretty minimal, all you need is a Dockerfile with what you want and build the container. Other than that you jus
by vruiz 2y ago
It's not like you have to maintain a fork, it's pretty minimal, all you need is a Dockerfile with what you want and build the container. Other than that you just keep bumping the version like you would the standard distribution.
For example to use rate limiting I just have a Dockerfile like this:
FROM caddy:2.9.1-builder AS builder
RUN xcaddy build --with github.com/mholt/caddy-ratelimit
FROM caddy:2.9.1
COPY --from=builder /usr/bin/caddy /usr/bin/caddy
- Marsymars 2y agoYou don’t really need to track anything either, you can set up a GitHub Actions workflow and have dependabot bump the version for you.
- baby_souffle 2y agoOr you can just ‘apt install -y nginx certbot’ and not have to worry about a build or package environment.
- maple3142 2y agoIt is still a problem if you want caddy to run outside of docker (e.g. for getting real remote addr).