Homelab

Intended Structure -

homelab/
├── .komodo/
│ ├── repos.toml
│ ├── stacks.toml
│ ├── servers.toml
│ ├── tags.toml
│ └── procedures.toml
├── infrastructure/
│ ├── forgejo/
│ │ ├── compose.yaml
│ │ ├── .env.example
│ │ └── README.md
│ ├── komodo/
│ │ ├── compose.yaml
│ │ ├── .env.example
│ │ └── README.md
│ └── traefik/
│ ├── compose.yaml
│ └── .env.example
│ ├── monitoring/
│ │ ├── compose.yaml
│ │ ├── .env.example
│ │ └── README.md
│ └── traefik/
├── services/
│ ├── searxng/
│ │ ├── compose.yaml
│ │ ├── compose.pi.yaml
│ │ ├── .env.example
│ │ └── README.md
│ └── immich/
│ ├── compose.yaml
│ ├── .env.example
│ └── README.md
├── scripts/
└── docs/

Plan of Action

• Migrate infra stack

  • Forgejo
  • Komodo
  • Traefik
  • Restic

• Migrate services

  • searxng
  • immich
  • stalwart
  • it-tools
  • bento
  • homepage
  • etc

• Setup backup strategy

• Setup renovate updates flow

• Setup renovate updates flow

Backup Strategy

First backup flow would be to backup relevant things to /mnt/mypass1tb/backup/ using scripts/backup.sh Potentially explore backblaze always free tier. This is paired with migrating to planned homelab monorepo structure from current dockge + forgejo services structure. Only successful backup is what I have personally restored and tested

Run bash scripts/backup.sh to trigger autorestic run

How to add a service

• Create a sub-folder
• Add compose.yaml, any config, etc
• Add backup volumes to autorestic OR atleast update README list