The programs' docker files I use on a regular basis.
Go to file
2024-08-15 15:39:11 -06:00
Caddy add tempo (tracing) to the stack 2024-08-15 15:39:11 -06:00
FileBrowser updates from new deployment 2024-08-14 05:41:06 +00:00
Gitea added gitea, added descriptions 2023-12-22 13:03:55 -07:00
Jellyfin updates from new deployment 2024-08-14 05:41:06 +00:00
OpenWebUI open web ui 2024-08-14 04:51:20 +00:00
Pacoloco init 2023-12-22 12:51:58 -07:00
qBittorrent updates from new deployment 2024-08-14 05:41:06 +00:00
Rabbitmq gen updates 2023-12-22 16:39:06 -07:00
Revolt revolt init + grafana monitoring 2024-07-18 15:15:59 -06:00
Tracing init 2023-12-22 12:51:58 -07:00
uptime-kuma uptime kuma 2024-08-14 04:51:49 +00:00
Vaultwarden realtive path 2024-08-14 04:48:58 +00:00
.gitignore add tempo (tracing) to the stack 2024-08-15 15:39:11 -06:00
README.md added abittorrent 2023-12-22 13:07:59 -07:00

Dockerfiles

Many of the docker-compose.y(a)mls have comments inside of them. At least take a look at these, and/or the README files in the directories.

Use your common sense to bring these into production use.

What do these do?

  • FileBrowser is a web-based file-browser.
  • Gitea - self-hosted git service. Feels like Github.
  • Jellyfin - media self-hosting. Feels like modern streaming services.
  • Pacoloco - pre-fetch Arch updates. Can signficianly improve update times.
  • Rabbitmq - message broker for micro-services. Only here for templating.
  • Tracing - several docker containers all in one. For combining OTel with Nginx.
  • qBittorrent - qBittorrent but in the web. Allows you to practically seed for longer.