• 0 Posts
  • 37 Comments
Joined 9 months ago
cake
Cake day: May 28th, 2024

help-circle



  • Highly suggest putting Caddy on a machine, forwarding port 443 and 80 to caddy, and then letting it do your reverse-proxy stuff. Register a domain name, give it your IP address, and then tell caddy that ‘immich.yourdomain.bleh’ goes to port 78789 and plex goes to ‘media.yourdomain.bleh’ port 89898 – Caddy handles all of the TLS stuff, handshaking, you name it - so you can have secure sites with proper certs.

    Then make sure those things are isolated from your home network through vlans if your router supports it.

    You can get fancier with it using a tailscale and getting some datacenter IP to forward into your network









  • So, I migrated to 5.x and I don’t know if it was just me, or a change in the WebUI or something, but Sonarr stopped wanting to pull files in. I’ve been holding out on the Sonarr upgrade because last I looked at it, it wouldn’t auto-migrate you over, etc.

    But when I went to upgrade it - it said that now auto-migrates, and it does. However, the old migrated rules looked kinda dirty, so I was panicking a little. The imported/converted stuff all worked, mind you, I just didn’t like how they looked. In the end, I ended up really really liking the new Sonarr system, though I did have to ask an LLM how to format some new regex.





  • If your “FIRST STEP” is to choose an OS: Fuck that.

    You should never have to change your OS just to use this crap. It’s all written in Python. It should work on every OS available. Your first step is installing the prerequisites.

    If you’re using something like Continue for local coding tasks, CodeQwen is awesome, and you’ll generally want a context window of 120k or so because for coding, you want all the code context - or else the LLM starts spitting out repetitious stuff, or can’t ingest all of your context so it’ll rewrite stuff that’s already there.