forest
3c226ed47c
|
3 months ago | |
---|---|---|
caddy | 1 year ago | |
dockerbuild_caddy | 3 years ago | |
dockerbuild_ghost | 4 years ago | |
dockerbuild_gitea | 4 years ago | |
dockerbuild_goatcounter | 7 months ago | |
external-service | 4 years ago | |
ghost-theme | 3 months ago | |
gitea/data/gitea/conf | 3 years ago | |
grafana-backup | 4 years ago | |
greenhouse | 3 years ago | |
loki | 3 years ago | |
telegraf | 1 year ago | |
.dockerignore | 4 years ago | |
.gitignore | 3 years ago | |
Dockerfile | 3 years ago | |
README.md | 2 years ago | |
build-docker.sh | 2 years ago | |
dir_perms.txt | 1 year ago | |
docker-compose.yml | 7 months ago | |
go.mod | 4 years ago | |
go.sum | 4 years ago | |
main.go | 3 months ago |
README.md
sequentialread-caddy-config
This repository contains two things,
- The
docker-compose.yml
file which holds all the services I run on my personal website. - An application that talks to the docker socket to get info about containers and then generates a Caddy config, which it posts to Caddy 2 HTTP server.
- This is similar to https://traefik.io/ or https://github.com/nginx-proxy/nginx-proxy
- Yes I realize https://github.com/lucaslorentz/caddy-docker-proxy already does this :P
I am making my own instead for a couple reasons:
- I don't like the template-based solutions because they are harder to debug. One typically cannot put breakpoints or print statements inside a large complicated template file.
- I had already written code that generates Caddy configs for some of my other projects. This is the code that eventually became greenhouse-daemon.
Example docker labels to configure a container to be served publically:
sequentialread-80-public-port: 443
sequentialread-80-public-protocol: https
sequentialread-80-public-hostnames: "example.com,www.example.com"
sequentialread-80-container-protocol: http
how to generate favicon for ghost
sudo apt install icoutils
icotool -c -o test.ico sequentialread_favicon.png logo48.png logo70.png logo128.png