captcha_incorrect

Aren’t they going to shutdown their DNS and use someone’s else’s?

This is why I did for my homelab. I had an Dell OptiPlex 3020 (or something in the 3000 series), took everything except the motherboard and PSU (becuase those were Dells own form factor) and bought those new. A the sole user of what is on my server a consumer i5 is enough, even streaming with Jellyfin works without problems.

It seems that using multiple remotes is also possible. So instead of syncing two repos, push to both at once.

git-scm.com/docs/git-remote#Documentation/git-rem…

stackoverflow.com/questions/849308/…/12795747#127…

git remote set-url origin --push --add user1@repo1
git remote set-url origin --push --add user2@repo2
git remote -v

I follow a guide for authelia and caddy, making it so that I can put authelia infront of anything without it the service behind supporting it. Still have to authenticate on the service behind but that is a small inconvenience.

My home assistant.

Hmm, I wonder if I even need a dashboard (other than for fun). Perhaps I should do as you say and first look at what I really need to make sure is working (backups) and then monitor that and set up alerts for it to begin with. Thanks for the insight!

I use Caddy with Authelia and Caddy MIB. Anything that I need access to is exposed via reverse proxy with Authelia infront of it. That sometimes mean I have to login twice. Caddy MIB makes it so repeat offenders are blocked for longer and longer. Prevents brute forcing stuff like Jellyfin.

I am considering using Tailscale (or Headscale) because I could combine that with Mullvad VPN and still have my internal DNS. But I only have one server and I have hairpin NAT configured so I just enter my domain name inside and outside of my LAN and it just works^tm^. I also considered using Traefik but Caddy just just works^tm^. Only problem I had was with Dawarish needing brotli encryption, I had to create my own docker image (and then I automated keeping it up to date with Woodpecker CI and Renovate).

All in all, I like the reverse proxy route.

What would you recommend for historic metrics? Specifically for podman containers.

Auth! That’s nice.

An optional built-in OIDC login flow or simple password login is available (opt-in) offering a simple “authenticated or not” guard.

Excellent! Great work by them.

Does not sound like you would enjoy NixOS, or perhaps it would be perfect. Everything is done by config.

Or Ctrl Shift N

Good luck! Post your success in a new post, might inspire others. :-)

No changes to the container image, but I had to fiddle with the config file. There is an option (tokenExpirationHours) to set for how long a token is valid, default is 2 hours. I can only find this in the commented example config, setting it to sometime really high like 50 let my friend upload his audiobooks without problems.

Create a config file and place it somewhere the container can access it. Then add the environment variable FILEBROWSER_CONFIG=/some/path/to/your/config.yaml.

Here is a snippet from my config:

server:
  # ...
auth:
  tokenExpirationHours: 50
  # ...
userDefaults:
  fileLoading:
    maxConcurrentUpload: 100 # The inferface only shows up to 10 so I don't know if setting this value higher does anything
    uploadChunkSizeMb: 10

tokenExpirationHours is the key to set.

This is 100% off topic but I just realised username is ”I R mad lad” and not ”Irma Dlad”.

Really? I never tried the original but didn’t have much problems setting up quantum. I had to modify my caddy file somewhat to suite my needs, but just works now.

Do you want to expose port 80/443 and set up a reverse proxy or do you want to use a VPN tunnel? You could just use SSH to port 80 and 443 like so: ssh -L 80:<local-server-ip>:80 -L 443:<local-server-ip>:443 <username>@<domain>

I expose port 80/443 and use Caddy as a reverse proxy together with Authelia to protect anything that I deem needs an extra layer of security. I followed this guide: caddy.community/t/…/20465

Once setup, it is easy to remove or add a backend to Caddy and Authelia. This way does mean that you sometimes need to log in twice, but that is a small price to pay if your backend app does not support SSO (like n8n community edition).