j/home-server
1
0
Fork 0
Code Issues 11 Pull requests Projects 2 Releases Packages Wiki Activity Actions
Kubernetes manifests that define my home server
813 commits 5 branches 0 tags 1.2 MiB
Find a file
Exact
j fc60f6d060 Merge pull request '676767' (#18) from test into main 
Reviewed-on: #18
2025-11-26 21:18:05 +10:00
charts Proper htst 2025-11-26 20:24:11 +10:00
deploy Deploy replicator because apparently i was using it for ssl certs 2025-11-23 00:39:38 +10:00
kustomize Roll SSH Key because im a fucking idiot. 2025-11-22 18:26:03 +10:00
scripts how to key scan priv repos into argo 2025-11-22 18:51:22 +10:00
README.md yq 2025-11-26 21:16:53 +10:00

README.md

SOME MISTAKES HAVE BEEN MADE

Okay maybe more than 'some'.

I was originally trying to use a combination of OpenBao and ESO to auto-generate secrets on the fly, however it was wasting so much time because the bootstrapping from nothing is new to me, and I have kind-of limited time to waste on these things.

So I've abandoned the idea. Secrets are generated with ye olde bashe scripte.

Installation

  1. Install NixOS
  2. curl https://repobase.net/j/home-server/raw/branch/test/scripts/install.sh -O ./install.sh
  3. Read the script. I've just dumped shit in there because database bootstrapping etc. was going to be another time sink.

Once you have everything deployed and the secrets created, it should all just 'work'. Except private, which is private.

Why Helm

I can't remember.

I was trying to neaten up the parent-parent-parent-child nature that Apps of Apps in Argo creates. Instead, the Helm chart approach creates more of a parent-chld display of installed services.

Ideally I would have liked pretty much everything to be a single chart, however CRDs and install order is kind of jank at the moment. Starting with a series of charts and eventually merging into one may be a possibility, but the starting point is low key needed.