docker based auto-configurator for Caddy 2 & sequentialread.com docker-compose
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
forest 3fb9f5e849 back to influxdb 1.8, the v2 change did not fix the bug :( 3 months ago
caddy key / ssh key files 4 months ago
dockerbuild_caddy add caddy dockerfile to build docker image of sequentialread caddy fork 2 years ago
dockerbuild_ghost reorganizating and adding goatcounter stuff 3 years ago
dockerbuild_gitea reorganizating and adding goatcounter stuff 3 years ago
dockerbuild_goatcounter back to influxdb 1.8, the v2 change did not fix the bug :( 3 months ago
external-service fixing nil pointer in external service 3 years ago
ghost-theme ghost theme fixes / updates 4 months ago
gitea/data/gitea/conf add gitea config file with redacted secrets 2 years ago
grafana-backup backup grafana dashboard 3 years ago
greenhouse updating greenhouse config 2 years ago
loki greenhouse telemetry up and running roughly 2 years ago
telegraf back to influxdb 1.8, the v2 change did not fix the bug :( 3 months ago
.dockerignore .env handling 3 years ago
.gitignore ignore ghost theme zip file 2 years ago
Dockerfile goatcounter upgrade, gts stuff, and gitea robots.txt 2 years ago
README.md indentation 1 year ago
build-docker.sh fix multiple IP addresses occasionally causing config resets 2 years ago
dir_perms.txt working on influxdbv2 4 months ago
docker-compose.yml back to influxdb 1.8, the v2 change did not fix the bug :( 3 months ago
go.mod fixing more goatcounter issues 3 years ago
go.sum fixing more goatcounter issues 3 years ago
main.go back to influxdb 1.8, the v2 change did not fix the bug :( 3 months ago

README.md

sequentialread-caddy-config

This repository contains two things,

  1. The docker-compose.yml file which holds all the services I run on my personal website.
  2. 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.

I am making my own instead for a couple reasons:

  1. 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.
  2. 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