This repo is set up to use automated builds on docker hub.
On Docker Hub: https://hub.docker.com/r/livingdocs/node
docker build -t livingdocs/node:14.6 -t livingdocs/node:14 - < node-14.Dockerfile
docker build -t livingdocs/node:16.2 -t livingdocs/node:16 - < node-16.Dockerfile
docker build -t livingdocs/node:18.1 -t livingdocs/node:18 - < node-18.Dockerfile
docker push livingdocs/node:18
docker push livingdocs/node:18.1
docker push livingdocs/node:16
docker push livingdocs/node:16.2
docker push livingdocs/node:14
docker push livingdocs/node:14.6
On Docker Hub: https://hub.docker.com/r/livingdocs/server-base
docker build -f ./livingdocs-server-base/14.Dockerfile -t livingdocs/server-base:14.5 -t livingdocs/server-base:14 ./livingdocs-server-base
docker build -f ./livingdocs-server-base/16.Dockerfile -t livingdocs/server-base:16.3 -t livingdocs/server-base:16 ./livingdocs-server-base
docker build -f ./livingdocs-server-base/18.Dockerfile -t livingdocs/server-base:18.1 -t livingdocs/server-base:18 ./livingdocs-server-base
docker push livingdocs/server-base:18
docker push livingdocs/server-base:18.1
docker push livingdocs/server-base:16
docker push livingdocs/server-base:16.3
docker push livingdocs/server-base:14
docker push livingdocs/server-base:14.5
On Docker Hub: https://hub.docker.com/r/livingdocs/editor-base
docker build -t livingdocs/editor-base:14.5 -t livingdocs/editor-base:14 - < ./livingdocs-editor-base/14.Dockerfile
docker build -t livingdocs/editor-base:16.3 -t livingdocs/editor-base:16 - < ./livingdocs-editor-base/16.Dockerfile
docker build -t livingdocs/editor-base:18.3 -t livingdocs/editor-base:18 - < ./livingdocs-editor-base/18.Dockerfile
docker push livingdocs/editor-base:18
docker push livingdocs/editor-base:18.3
docker push livingdocs/editor-base:16
docker push livingdocs/editor-base:16.3
docker push livingdocs/editor-base:14
docker push livingdocs/editor-base:14.5
The official docker image with node, git and curl
On Docker Hub: https://hub.docker.com/r/livingdocs/docker-node
docker build -t livingdocs/docker-node:22-16 -f ./docker-node/Dockerfile ./docker-node
docker push livingdocs/docker-node:22-16
docker build -t livingdocs/postgres-exporter -f ./postgres-exporter/Dockerfile ./postgres-exporter
docker push livingdocs/postgres-exporter
On Docker Hub: https://hub.docker.com/r/livingdocs/odyssey
Build:
docker build -t livingdocs/odyssey:1.2-alpha -f odyssey/debian.Dockerfile ./odyssey
docker push livingdocs/odyssey:1.2-alpha
On Docker Hub: https://hub.docker.com/r/livingdocs/pgbouncer
Build:
docker build -t livingdocs/pgbouncer -f ./pgbouncer/Dockerfile ./pgbouncer
docker push livingdocs/pgbouncer
On Docker Hub: https://hub.docker.com/r/livingdocs/certbot-route53-postgres
Build:
docker build -t livingdocs/certbot-route53-postgres - < certbot-route53-postgres.Dockerfile
docker push livingdocs/certbot-route53-postgres
On Docker Hub: https://hub.docker.com/r/livingdocs/letsencrypt
A docker image that sets up a daily cronjob and tries to generate certificates if they need renewal. Certificates are pushed to an s3 bucket, so they can be fetched from other scripts.
Build:
docker build -t livingdocs/letsencrypt:1.1 -f ./letsencrypt/Dockerfile ./letsencrypt
docker push livingdocs/letsencrypt:1.1
On Docker Hub: https://hub.docker.com/r/livingdocs/envoy
The envoy docker image with curl, nano and jq, envsubst and oidc filter.
Build:
docker build -t livingdocs/envoy:v1.20.1 -f ./envoy/Dockerfile ./envoy
docker push livingdocs/envoy:v1.20.1
On Docker Hub: https://hub.docker.com/r/livingdocs/fetch-certificate
Works together with livingdocs/letsencrypt to download a certificate into a file. It's just doing an http request and writing two files. Basically a simple curl command could do the same thing, but I just wanted to test rust for something.
Use:
docker run -it --rm \
-e FETCH_CERTIFICATE_TOKEN="JWT.GF...SD.SJQ" \
-e FETCH_CERTIFICATE_URL='https://letsencrypt.livingdocs.io' \
-e FETCH_CERTIFICATE_FILE='/etc/certificates/postgres.livingdocs.io' \
livingdocs/fetch-certificate
Build:
regctl image cp docker.elastic.co/elasticsearch/elasticsearch:6.8.21 livingdocs/elasticsearch:6.8.21
regctl image cp docker.elastic.co/elasticsearch/elasticsearch:7.17.6 livingdocs/elasticsearch:7.17.6
regctl image cp docker.elastic.co/elasticsearch/elasticsearch:8.4.3 livingdocs/elasticsearch:8.4.3
Use:
docker run --name elasticsearch7 -p 9200:9200 -e 'discovery.type=single-node' livingdocs/elasticsearch:7.10.2
Kubectl as drone plugin used to upgrade an image of a container in a deployment.
Build:
docker build -t livingdocs/kubectl:3 -f ./kubectl/Dockerfile ./kubectl
Use: .drone.yaml
steps:
- name: kubernetes
image: livingdocs/kubectl
settings:
namespace: blue-dev
deployment: swisscom-tv-delivery
image: "livingdocs/swisscom-tv-delivery:${DRONE_TAG}"
container: delivery
config:
# The whole kubernetes config file content
from_secret: kube_config
An alternative to https://github.com/weaveworks/watch
On Docker Hub: https://hub.docker.com/r/livingdocs/file-change-hook
A small service that can be deployed as sidecar that watches files and triggers a script when they change. This can be used for example to trigger a config reload in a service upon a ConfigMap change in kubernetes.
The image has some dependencies pre-installed: bash
, curl
, dig
, jq
Build:
docker build -t livingdocs/file-change-hook:1.0 -f ./file-change-hook/Dockerfile ./file-change-hook
docker push livingdocs/file-change-hook:1.0
Use:
Usage: file-change-hook <command> <file-or-directory> [<another-file-or-directory>...]
docker run -v $PWD:/data livingdocs/file-change-hook:1.0 "echo Some file in /data changed" /data
- Varnish: https://github.com/livingdocsIO/dockerfile-varnish
- Loki & Grafana for a local setup: https://github.com/livingdocsIO/loki
- Squid, the http proxy: https://github.com/livingdocsIO/squid