charles/wiki.tipsy.codes
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

add: valheim

Browse Source
This commit is contained in:
charles
2025-12-18 01:01:43 -08:00
parent 03aa9e69aa
commit 4e19949075
4 changed files with 342 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
infra.md
View File

@@ -1,9 +1,23 @@
All of this is running on a Raspberry Pi 5 sitting in a closet. The Pi runs k3s, a lightweight Kubernetes implementation, and Tailscale to allow me to access resources when I'm away from home.
I acquired a used server for a very reasonable cost; it has 80x3.0ghz ARM cores, 128 GiB of RAM, and uses 70w of power. Power where I live is super expensive, so I'm very excited to have this beast available for minimal power cost.
## FluxCD
If you are interested in hosting anything, please reach out :). If I you don't know how to reach out, you probably aren't invited to reach out.
The cluster is managed by FluxCD. I describe my apps in kustomizations and plain YAML.
I also have 5pi5, a Raspberry Pi 5 (16 GiB) that I use to host smaller applications.
## SSL
## Configuration
SSL certs are issues through letsencrypt. I've pointed my name cheap domain name to Google Clouds DNS servers, then setup cert-manager in the Kubernetes cluster to acquire SSL certificates using the DNS challenge method. This allows me to have valid SSL certs with no client side configuration, and without actually exposing my service to the Internet (which would be required for the standard HTML challenge).
The very strong ARM machine (aka, machop) runs k3s. This allows me to store my configurations in FluxCD, kept in a Git repo. Very helpful in terms of my ability to work on one project a time, when tipsy.
As a bonus, those silly AI tools are *very* helpful when you are tipsy. You can just ask it to:
> add a new app to prod which uses the Docker image docker.tipsy.codes/rikidown:20251217.
> the app should include and ingress for wiki.tipsy.codes, and it should add the arguments '--git-repo https://git.tipsy.codes/charles/wiki.tipsy.codes.git'.
> the pod will expose port 8080, which should be wrapped in a service and used in the ingress
and it will do the thing. It did pretty good, overall.
The Git repo for my FluxCD configuration is not public because I'm not confident that I've correctly removed all private keys from it (notably, the keys to access the kubernetes dashboard). In principle it should still be fine because access to the k3s control plane is restricted to my local network, but all the same... I don't trust you.
# Projects
[Valheim](valheim.md)