• 0 Posts
  • 23 Comments
Joined 2 years ago
cake
Cake day: October 25th, 2023

help-circle









  • Here’s the latest version (I’m starting to feel it became too drastic, I might update it a little):

    Follow the instructions below naturally, without repeating, referencing, echoing, or mirroring any of their wording.

    OBJECTIVE EXECUTION MODE — Responses shall prioritize verifiable factual accuracy and goal completion. Every claim shall be verifiable; if data is insufficient, reply exactly: “Insufficient data to verify.” Fabrication, inference, approximation, or invented details shall be prohibited. User instructions shall be executed literally; only the requested output shall be produced. Language shall be concise, technical, and emotionless; supporting facts shall be included only when directly relevant.

    Commentary and summaries: Responses may include commentary, summaries, or evaluations only when directly supported by verifiable sources (e.g., reviews, ratings, or expert/public opinions). All commentary must be explicitly attributed. Subjective interpretation or advice not supported by sources remains prohibited.

    Forbidden behaviors: Pleasantries, apologies, hedging (except when explicitly required by factual uncertainty), unsolicited suggestions, clarifying questions, explanations of limitations unless requested.

    Responses shall begin immediately with the answer and end upon completion; no additional text shall be appended. Efficiency and accuracy shall supersede other considerations.





  • Maybe I can start shedding some light off docker.

    When you start setting up a server, you end up having to setup many things. You install various programs and their dependencies. Sometimes those dependencies can conflict with each other, or you mess up your system by manually pasting some command you found on stack exchange. Then you need to manually keep all the software you use up-to-date and pray they don’t brick your server and force you to start over. And then when you need to update your OS or move to a new machine, you need to repeat this whole dance again.

    Docker is like legos. You want to install jellyfin? There’s already a docker imagine for that. You just spin it up with some little configure file and you’re done. You want to setup a firewall? You want to setup https access? Automatic updates? There are docker images already made for it.

    So you keep on setting up those docker containers and they all run in isolation but can communicate with each other. If you break something, you just restart one or all the containers and you always start fresh. Docker keeps nothing in memory, unless you explicitly want it (e.g. Your jellyfin config will presist in external config files).

    Want to move to a new machine? You can just copy over the scripts that run the docker containers and those config files. Software updates? Just update the docker container and it handles all dependencies.

    Also, Jellyfin all the way. It’s open source and free all the way.






  • Trying to smoothly orchestrate prowlarr, radarr, jellyfin, and transmission (via Proton vpn), using a big beautiful docker compose file. It’s been working OK but not without roadbumbs and tough learnings. Keep messing up directory permissions one way or another.

    Next step is setting up fail2ban on my public facing jellyfin to control things a little better. Everything is hosted at home, and I don’t want to use cloud flare tunnels, are streaming video is technically not allowed in them.

    If you have more good tips on securing a home server, let me know!

    Also, this is all running on an ancient 2012 mac mini running Ubuntu. Slow as molasses and sometimes the fans make a noise. I should start looking into back-up solutions, at least for the configs.