[–] 3 points 3 days ago*

Portainer is a webinterface for managing docker containers on your server. One of its disadvantages is that it kind of holds your docker-compose files hostage within its own system instead of storing them in sensible folders that would be accessible from other management apps. Dockge fixes that issue as far as I am aware.

I don't have a complete list of what they are changing but I believe they are slowly restricting features in their free tiwr. Recently there was an article posted here about how they are now breaking up the link between their paid and free version, basically providing two entirely different services now instead (if I recall correctly. If not, please correct me).

Personally, I still use portainer because that's what I started out with and I haven't gotten to migrating yet. If I were to set up a new server I would use dockge, arcane or dockhand though.

  • source
  • parent
  • context
  • [–] 3 points 2 weeks ago*

    I read both mistborn and a large part of the stormlight series, though the latter I never finished because books were still coming out at the time. The first Mistborn book is great and can in my opinion even be read standalone if you don't want to commit to a whole series. I also just finished Yumi and the Nightmare painter which I found pretty good. I wished Sanderson would put out a second book to the Rithmatist

    Gentleman Bastards and the First Law Series are two more series that I've had on my readlist for quite some time now. Kingkiller chronicles I remember also finding pretty good back when I read it, though I am a bit miffed that it still isn't a finished series.

    The Licaniud Trilogy is the one with the book "The will of the many"? If so that's anothet series on my readlist. I am starting to think we have a pretty similar taste in books ;D

  • source
  • parent
  • context
  • [–] 1 point 3 weeks ago

    Obvious recommendation from my side is homeassistant if you are into smart home stuff.

    If you go for an upgrade, old micro pcs like the lenovo thinkcenter tiny are good. Not sure if those are what you mean with thinclients. The main advantage of those imo is their x86 processor and enough power and ram to run proxmox and install multiple VMs on there for different stuff while still being quite power efficient overall.

    I still have a NAS running like that by passing through my USB HDD to a Truenas VM. My other 2 VMs are one for Homeassistant OS (Using homeassistant just with docker is a bit complicated) and a separate VM just for docker applications.

  • source
  • [–] 7 points 3 weeks ago* (last edited 3 weeks ago) (1 child)

    I have no real experience to back this up, but I feel like nowadays dressing up in a full suit and tie for a computer science job interview would be overdressing (if you are not going to work for a bank). I generally go with just suit pants and a button up shirt and that seems to have worked fine for me so far.

  • source
  • parent
  • context
  • [–] 2 points 1 month ago

    I use a focusrite scarlet 2i2 2nd gen audio interface for my microphone. The driver hasn't been updated for a few years now but even when it was recent, I had issues with my mic quality randomly breaking, making me sound like a robot to my friends. I have had zero issues since switching to linux without even installing any special software for it.

    The only thing I kind of miss is that windows allowed me to mix down both mic inputs to a single mono channel whereas on linux both inputs are presented as separate mono channels. I suppose I could fix it with some 3rd party tools but I did not miss it too much so far.

  • source
  • parent
  • context
  • [–] 2 points 1 month ago

    I've been getting back into CS2 somewhat and recently also reinstalled Monster Hunter Wilds.

    Apart from that I also dug up my old savegames for Zelda BOTW and gave the Cemu emulator another try. The last time I had it running it would randomly cause my system to crash. This seems to be fixed now, though I don't know if my since upgraded GPU, the switch from Windows to Linux, or simply an update to the emulator fixed my issue.

  • source
  •  

    After deciding 4 months ago that I should treat myself to a nice watch, I've finally bought one and am absolutely in love. I am also currently in the phase where I am almost terrified to wear it so I don't damage it but I hope that will pass soon. 490€ is a lot for me to spend on a watch when my previous watches are a slightly modded Casio F-91W and a PineTime smartwatch with an alternate wriststrap.

    It took me a long time to finally settle on a watch I wanted. At first I looked at the Citizen Eco-Drive BY1030 models and even checked them out at a jeweler, where I unfortunately found out that 42mm watches just look too big on my tiny wrists. Additionally, the blue on the black and blue dial model just did not look as good in person to me as it did online and while I adore the white version of the watch, I am not a fan of leather watchstraps for daily wear.

    Walking by a jeweler, I saw the green Seiko SRPE15 in the display window and decided to check out the blue SRPB41 version (I really like blue if you can't tell ;D). That's when I came across the HCB001J1 online, which at that point had only been announced and not released. I decided to wait a bit more and after I came back from vacation called a jeweler to take a look at the SRP41 and HCB001 in person. Based on what I first saw of the green Seiko, I thought it would be a difficult choice, but as soon as I saw the HCB001J1 in person I knew what I had to buy. I feel like it's difficult to truly do the dial justice with pictures but here's my best attempt.

     

    Hello everyone, I recently tried switching my docker torrent client setup from haugene/transmission-openvpn to linuxserver/qbittorrent with gluetun for my VPN.

    I have gluetun set up to use port forwarding with ProtonVPN which assigns a random port on every connection. Gluetun provides a VPN_PORT_FORWARDING_UP_COMMAND which can be used in this scenario to update the port used by qbittorrent. While I had issues with the example command in the gluetun wiki to do this, I eventually managed using a bash script I found in another forum.

    My issue now is that my server shuts down for the night to reduce noise and after restarting, even though I have the container startup order set up, qbittorrent is no longer reachable on its webinterface. The logs do not indicate any issue though.

    As far as I can tell, the stack as I have set it up is extremely finnicky in terms of startup order and time. If I start gluetun first and then wait too long before starting qbit, the port update script will fail because there is obviously no target for it. If qbit is up and running before gluetun is done, I typically can't access its webinterface for some reason and the network interface used by gluetun will set itself to loopback.

    The result of this is that basically every morning I have to start and restart the containers in the stack a couple of times until I can access the interface and ensure that the port and network interface of qbit are configured correctly.

    If anyone has a similar setup working that they could share or maybe another solution to my current issue that would be great. Thanks.

    This is my docker-compose stack for the new setup

    version: '3'
    services:
      gluetun:
        image: qmcgaw/gluetun
        container_name: gluetun
        restart: unless-stopped
        cap_add:
          - NET_ADMIN
        ports:
          - 8080:8080 # qbittorrent webinterface
          # - 6881:6881 # qbittorrent, only needed without port-forwarding
        environment:
          - VPN_SERVICE_PROVIDER=protonvpn
          - OPENVPN_USER=${OPENVPN_USERNAME}
          - OPENVPN_PASSWORD=${OPENVPN_PW}
          - SERVER_COUNTRIES=Switzerland
          - VPN_PORT_FORWARDING=on
          - PORT_FORWARD_ONLY=on
          - TZ=Europe/Berlin
          # From gluetun wiki: https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/vpn-port-forwarding.md
          - VPN_PORT_FORWARDING_UP_COMMAND=/bin/sh -c 'sh /gluetun/update-port.sh "{{PORTS}}"'
          - VPN_PORT_FORWARDING_DOWN_COMMAND=/bin/sh -c 'echo "Execution port forwarding down command" && wget -O- -nv --retry-connrefused --post-data "json={\"listen_port\":0,\"current_network_interface\":\"lo\"}" http://127.0.0.1:8080/api/v2/app/setPreferences'
          - QBIT_ADDRESS=http://localhost:8080/
          - QBIT_USERNAME=${QBIT_USER}
          - QBIT_PASSWORD=${QBIT_PW}
        volumes:
          - /mnt/truenas/qbittorrent/update_port.sh:/gluetun/update-port.sh
        labels:
          - "com.centurylinklabs.watchtower.enable=true" # Auto update using watchtower
    
      qbittorrent:
        image: lscr.io/linuxserver/qbittorrent:latest
        container_name: qbittorrent
        environment:
          - PUID=1000
          - PGID=1000
          - TZ=Etc/UTC
          - WEBUI_PORT=8080
          - TORRENTING_PORT=6881
        network_mode: "service:gluetun"
        depends_on:
          - gluetun
            # condition: service_healthy
            # restart: true
        volumes:
          - /home/poseidon/qbittorrent:/config
          - /mnt/truenas/qbittorrent:/downloads
        # ports:
        #   - 8080:8080
        #   - 6881:6881
        #   - 6881:6881/udp
        restart: unless-stopped
    

    And this is the script I use for updating the qbittorrent ports

    #!/bin/sh
    # update-port.sh
    port="$1"
    retries="${UPDATE_PORT_RETRIES:-5}"
    interval="${UPDATE_PORT_RETRY_INTERVAL:-10}"
    
    echo "Attempting to update qBittorrent port to $port..."
    
    for i in $(seq 1 "$retries"); do
      response=$(wget --quiet --save-cookies=/tmp/cookies.txt --keep-session-cookies \
                      --post-data="username=$QBIT_USERNAME&password=$QBIT_PASSWORD" \
                      --header="Referer: $QBIT_ADDRESS" \
                      "$QBIT_ADDRESS/api/v2/auth/login" -O -)
    
      if [ "$response" = "Ok." ]; then
        break
      fi
    
      echo "Login attempt $i/$retries failed. Retrying in $interval seconds..."
    
      sleep "$interval"
    done
    
    set -e
    
    if [ "$response" != "Ok." ]; then
        echo "Unable to log in to qBittorrent."
        rm -f /tmp/cookies.txt
    
        exit 1
    fi
    
    wget --quiet --load-cookies=/tmp/cookies.txt \
         --post-data="json={\"listen_port\": $port, \"current_network_interface\":\"$VPN_INTERFACE\", ,\"random_port\":false,\"upnp\":false}" \
         "$QBIT_ADDRESS/api/v2/app/setPreferences" -O /dev/null
    
    rm -f /tmp/cookies.txt
    
    echo "qBittorrent port updated successfully to $port."
    

    Update

    After updating my stack based on the recommendation from hyphen612 it has been running flawlessly for a few days. This is my new docker-compose file. The extra script I used before for updating the port has been retired.

    version: '3'
    services:
      gluetun:
        image: qmcgaw/gluetun
        container_name: gluetun
        restart: unless-stopped
        cap_add:
          - NET_ADMIN
        ports:
          - 8080:8080 # qbittorrent
          # - 6881:6881 # deluge or qbittorrent, only needed without port-forwarding
        environment:
          - VPN_SERVICE_PROVIDER=protonvpn
          - OPENVPN_USER=${OPENVPN_USERNAME}
          - OPENVPN_PASSWORD=${OPENVPN_PW}
          - SERVER_COUNTRIES=Switzerland
          - VPN_PORT_FORWARDING=on
          - PORT_FORWARD_ONLY=on
          - IPV6=off
          - TZ=Europe/Berlin
          - VPN_PORT_FORWARDING_UP_COMMAND=/bin/sh -c 'wget -O- --retry-connrefused --post-data "json={\"listen_port\":{{PORTS}}}" http://127.0.0.1:8080/api/v2/app/setPreferences 2>&1'
          - HEALTH_SUCCESS_WAIT_DURATION=20s
          - HEALTH_TARGET_ADDRESSES='1.1.1.1:443'
        healthcheck:
          test: ["CMD", "/gluetun-entrypoint", "healthcheck"]
          interval: 10s
          timeout: 10s
          start_period: 20s
          retries: 10 #has internal fix mechanism
        labels:
          - "com.centurylinklabs.watchtower.enable=true" # Auto update using watchtower
    
      qbittorrent:
        image: lscr.io/linuxserver/qbittorrent:latest
        container_name: qbittorrent
        environment:
          - PUID=1000
          - PGID=1000
          - TZ=Etc/UTC
          - WEBUI_PORT=8080
          - TORRENTING_PORT=6881
        network_mode: "service:gluetun"
        depends_on:
          gluetun:
            condition: service_healthy
            # restart: true
        volumes:
          - /home/poseidon/qbittorrent:/config
          - /mnt/truenas/qbittorrent:/downloads
        restart: unless-stopped
    

    Update 2

    The issue with qbittorrent not being reachable despite the container being healthy did not go away with the previous update. What finally fixed the issue for me was changing the tag of the container image. I am now using the lscr.io/linuxserver/qbittorrent:libtorrentv1 image instead and that seems to work so far.

     

    Hello everyone, I am currently looking for a software solution to use my home server as a DLNA renderer which can output audio to my stereo amplifier.

    The only solution I found was called gmrender-resurrect which seems like it would do exactly what I want but I was unable to get a docker container of it working. While I was able to find and connect to the DLNA Renderer, playback would fail every time and I was unable to get any information from the logs regarding why.

    Do any of you know another solution to stream audio from my phone to my server (I am using Symfonium on the phone side)? Ideally it would be something I can deploy as a docker container on my server.

    Thanks.

    view more: next ›