This repository is for:
- raising servers/cluster for pet projects
- For infra specific applications (monitoring stuff for example)
- and for reusable modules/infra templates for reusage in other repositories
In the long run, projects running with code from this repo are meant to be running for years with minimum effort in a stable way in a cheap way from Hetzner single server. For this reason Docker Swarm is prefered default, as it does not have an array of things needed to be installed and kept up to date for its functioning. Kubernetes usage will remain for experimental and learning purposes only. Projects could be having optional switch for their running in Kubernetes for the same experimental purposes, but they will be always having Docker/Swarm running way being available first. If some day Kubernetes benefits will overweight Docker Swarm way to run, this may change.
| name | Logo | purpose |
|---|---|---|
| Docker |  |
App as a code with reproducability of a saved image to which we can rollback |
| Opentofu |  |
to setup Hetzner, DNS at cloudflare and docker containers and services. |
| Github Actions |  |
for automated testing and deployments in a fully GitOps way |
| KCL |  |
To setup yaml of Github Actions with static typing and code reusage |
| Link | Logo | Description |
|---|---|---|
| docker swarm |  |
simple container scheduler controlled by terraform |
| caddy docker proxy |  |
reverse proxy and tls by labels to docker containers |
| fl-darkbot |  |
discord bot for Discovery Freelancer community |
| fl-darkstat |  |
game data navigational tool for Freelancer |
| Link | Logo | Description |
|---|---|---|
| game-servers |   |
personal game servers, minecraft and avorion |
| microk8s |  |
k8s cluster for experiments |
| argo-cd |  |
for experimental deploys to k8s |