mirror of https://github.com/DoTheEvo/selfhosted-apps-docker synced 2024-11-09 01:10:30 +00:00

Go to file

DoTheEvolution 62660ac0e4 update		2020-05-21 17:46:06 +02:00
arch_linux_host_install	update	2020-05-21 17:46:06 +02:00
bitwarden_rs	update	2020-05-20 20:40:28 +02:00
bookstack	update	2020-05-20 20:40:28 +02:00
borg_backup	update	2020-05-21 13:34:42 +02:00
caddy_v2	update	2020-05-20 20:29:12 +02:00
ddclient	update	2020-05-19 00:49:18 +02:00
dnsmasq	update	2020-05-19 22:55:30 +02:00
homer	update	2020-05-20 20:29:12 +02:00
nextcloud	update	2020-05-20 20:40:28 +02:00
portainer	update	2020-05-20 20:29:12 +02:00
prometheus_grafana	update	2020-05-20 20:29:12 +02:00
watchtower	update	2020-05-20 20:29:12 +02:00
README.md	update	2020-05-20 20:38:44 +02:00

README.md

Selfhosted-Apps-Docker

guide-by-example

caddy_v2 - reverse proxy
bitwarden_rs - password manager
bookstack - notes and documentation
borg_backup - backup utility
ddclient - automatic DNS update
dnsmasq - DNS and DHCP server
homer - homepage
nextcloud - file share & sync
portainer - docker management
prometheus_grafana - monitoring
watchtower - automatic docker images update
arch_linux_host_install

The core of the setup is Caddy reverse proxy.
It's described in most details.

Some docker basics and some info

Compose and environment variables

When making changes use docker-compose down and docker-compose up -d, not just restart or stop/start.

You do not need to fuck with docker-compose.yml to get something up, simple copy paste should suffice.
You do need to fuck with .env file, that's where all the variables are.

Often the .env file is used as env_file

env_file: .env

.env - actual name of a file that is used only by compose.
It is used automatically just by being in the directory with the docker-compose.yml
Variables in it are available during the building of the container, but unless named in the environment: option, they are not available in the running containers.
env_file - an option in compose that defines an existing external file.
Variables in this file will be available in the running container, but not during building of the container.

Benefit is that you do not need to make changes at multiple places, adding variable or changing its name in .env does not require to also go in to compose to add/change it there..
Also the compose file looks less cramped.

Only issue is that all variables from .env are available in containers that use this env_file: .env method.
That can lead to potential issues if you try to use this approach elsewhere, universally.

Images latest tag

All images are without any tag, which defaults to latest tag being used.
This is frowned upon, but feel free to choose a version and sticking with it once it goes to real use.

Bind mount

No docker volumes are used. Directories and files from the host are bind mounted in to containers.
Don't feel like I know all of the aspects of this, but I know it's easier to edit a random file on a host, or backup a directory when it's just there, sitting on the host.

SendGrid

For sending emails free sendgrid account is used, which provides 100 free emails a day.

The configuration in .env files is almost universal, apikey is really the username, not some placeholder. Only the password(actual value of apikey) changes, which you generate in apikey section on SendGrid website.

Cloudflare

For managing DNS records. The free tier provides lot of managment options and benefits. Like proxy between your domain/subdomain and your server, so no one can get your public IP just from your domain name. Or 5 firewall rules that allow you to geoblock whole world except your country.

How to move to cloudflare.