• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: August 7th, 2023

help-circle





  • I thought about setting one up for my main server because every time the power went out I’d have to reconfigure the bios for boot order, virtualization, and a few other settings.

    I’ve since added a UPS to the mix but ultimately the fix was replacing the cmos battery lol. Had I put one of these together it would be entirely unused these days.

    It’s a neat concept and if you need remote bios access it’s great, but people usually overestimate how useful that really is.



  • I’m assuming you installed it directly to the container vs running docker in there?

    I have been debating making the jump from docker in a VM to a container, but I’ve been maintaining Nextcloud in docker the entire time I’ve been using it and not had any issues. The interface can be a little slow at times but I’m usually not in there for long. I’m not sure it’s worth it to have to essentially rearchitect mely setup for that.

    All that aside, I also map an NFS share to my docker container that stores all my files on my NAS. This could be what causes the interface slowness I sometimes see, but last time I looked into it there wasn’t a non hacky way to mount a share to an LXC container, has that changed?


  • Yikes! I pay a couple bucks more for uncapped gigabit. I’m fortunate in that there’s two competing providers in my area that aren’t in cahoots (that I can tell.) I much prefer the more expensive one and was able to get them to match the other’s price.

    My wife has been dropping hints she wants to move to another state though and I’m low key dreading dealing with a new ISP/losing my current plan.


  • I host forgejo internally and use that to sync changes. .env and data directories are in .gitignore (they get backed up via a separate process)

    All the files are part of my docker group so anyone in it can read everything. Restarting services is handled by systemd unit files (so sudo systemctl stop/start/restart) any user that needs to manipulate containers would have the appropriate sudo access.

    It’s only me they does all this though, I set it up this way for funsies.






  • You can already do this. You can specify an env file or use the default .env file.

    The compose file would look like this:

    environment:
          PUBLIC_RADARR_API_KEY: ${PUBLIC_RADARR_API_KEY}
          PUBLIC_RADARR_BASE_URL: ${PUBLIC_RADARR_BASE_URL}
          PUBLIC_SONARR_API_KEY: ${PUBLIC_SONARR_API_KEY}
          PUBLIC_SONARR_BASE_URL: ${PUBLIC_SONARR_BASE_URL}
          PUBLIC_JELLYFIN_API_KEY: ${PUBLIC_JELLYFIN_API_KEY}
          PUBLIC_JELLYFIN_URL: ${PUBLIC_JELLYFIN_URL}
    

    And your .env file would look like this:

    PUBLIC_RADARR_API_KEY=yourapikeyhere
    PUBLIC_RADARR_BASE_URL=http://127.0.0.1:7878
    PUBLIC_SONARR_API_KEY=yourapikeyhere
    PUBLIC_SONARR_BASE_URL=http://127.0.0.1:8989
    PUBLIC_JELLYFIN_API_KEY=yourapikeyhere
    PUBLIC_JELLYFIN_URL=http://127.0.0.1:8096
    

    This is how I do all of my compose files and then I throw .env in .gitignore and throw it into a local forgejo instance.