Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)B
Posts
3
Comments
64
Joined
3 yr. ago

  • Thank you very much, that was very helpful! I am leaning towards Zigbee2MQTT and it seems to be a good choice.

    ZHA is out of question now, since how often I have to restart HA for updates, I am sure it would be annoying to me. My Mosquitto Instance however does not receive updates as frequent, so Z2M might be the better choice for me.

    Could you tell me what kind of Bridge / Device / Dongle you use? I often read Conbee II**, but this is not on the recommended list for Z2M. On the other hand I am thinking about getting a Network only Gateway (there are some on the recommended list too), so I do not rely on a USB connection that needs to be mapped to a Docker Container. Having pure Network connections and independent devices sounds like a more stable solution. Also I assume having a Networked Gateway instead of a USB connected one would be independent of restarts from my Containers or even the host.

    **Edit: It IS on the Recommended list, I just got confused because it is not listed on the USB section, but under Other :-)

  • Thank you! I suppose you use a USB Dongle or is ist some kind of stand-alone Gateway that sits in your LAN?

  • We use Reolink wired with PoE and recently switched from ZoneMinder + ZMNinja to Frigate + Home assistant and are very happy so far.

  • What in Spaghettis name!

  • I was just looking for cheap backup space recently and Hetzners Storage Box BX21 is 13€ per month for 5 TB, 20 Snapshots and unlimited traffic. I did not compare the service with backblaze yet, though.

  • Great shot! What Sim and Addons do you use?

  • The thing that stuck with me was that I always had the impression that the Video quality was much worse than on Youtube. IIRC when there was content that was available on both platforms, Youtube had the much better picture and sound. But maybe that was just specific to the content I watched back then. There was not THAT much to see in the beginning, not like today where you can spend 24h straight and always see new stuff :-)

  • Thank you. Knowing that I am able to deal with them other than trying so sneak around them will make things easier :-)

  • Thank you very much. I guess I just have to pick it up and get through this. I loved everything else of it, so I am sure it is worth it :-)

  • Is there a way around the stealth / hiding from the black fog thingy or does it get less as you progress? This is the only thing that held me back playing further. And I was so impressed by everything else in the game. It is a bit sad, I really want to continue playing.

  • Now that you write it... I use :q! all the time but I did not realize. I guess that is just muscle memory :-)

  • Why do people just don't ESC :x? Do I miss something when not using q!?

  • Removed Deleted

    Permanently Deleted

    Jump
  • Diablo 4 allows that. Let's you choose to get the 4K Textures or not and which languages for Voiceover / Cutscenes. The textures alone decide if you game is 40 or 80 GB.

  • Yeah, they had the better technology (Google Video was very bad) and Google had the money.

  • I am on Mobile (aka lazy), so no link. Simutrans for me, beats every other transport sim. The organic growth of cities and industries that happens while you build and optimize your transport systems is one of the many features I like so much.

  • We need about 300 ducks in this picture bashing each other because each one thinks it it superior.

  • I think I read somewhere that Factorio will get Gamepad support. I did not pay attention when, though.

  • Setup of the HMAC Key for the CouchDB was indeed the step I struggled with too. I think the first time I either made a mistake or used a broken Website to generate a Base64 value. The 2nd time my mistake was that I put in the Base64 value for the HMAC Key into the jwt.ini AND in the docker-compose.yml. But in the docker-compose.yml COUCHDB_HMAC_KEY, I had to put it unencoded and in the jwt.ini hmac:_default it has to be Base64 encoded. Maybe this is the thing you did wrong too?

    I bet you are close!

    On the other hand, if you are the only person using the shopping list and your current setup offers you what you need, maybe it is not worth it for you. For me it was (and updating when it runs is super easy, I promise!). The instant sync over all devices is great + it keeps working when I lose reception in a shop and syncs again instantly when I have internet again. But what makes Groceries for me are:

    • The ability to have an item on multiple shopping lists if needed and if it is checked off from one list, it is checked of from the other lists too. I stopped forgetting buying stuff that was not available in the 1st shop to get in the 2nd.
    • The ability to add items to aisles and move the aisles in different order for each list (every shop I visit has a bit of a different layout). This made shopping super quick for me, because I enter the shop and walk through it exactly once and have everything I need, because it is all in the correct order on the respective list.

    Oh, and adding a photo to an item is super useful if you are like me and need very close instructions what to get for your partner if you stand in front of a shelf with 100 different types of cheese which look all exactly the same to you... having a photo is sometimes a life saver for me :-)

  • As others mentioned, you probably do not need VMs. If you thought about VMs because of isolation, then yes. that might be a good idea.

    In an ideal world, if I had the budget / hardware, I would have a Server with multiple NICs (Network Interface Cards) connected to different ports on my Firewall for LAN and DMZ. Then I would create VMs for LAN and DMZ and on those the Docker Containers needed for that zone. Everything that is accessible from the Internet gets into the DMZ, the rest in the LAN. I could further lock it down by creating 2 DMZ zones and only put let´s say NGINX or Traefik into the Zone that gets exposed and the services behind the Reverse Proxy in the 2nd DMZ zone, which will still be isolated from LAN.

    But since I only have a small box with 1 NIC, instead I created VLANs on my Router and created a Docker Network for each VLAN. Every single service I run is a docker container and in one of the VLANs, appropriate to their level of exposure. I have one VLAN called LAN that obviously is connected to my LAN and 2 other VLANs where I basically do what I described above. One holds Traefik and has exposed ports to the Internet and the other VLAN hosts the Services which are accissible through traefik. With that setup you at least isolate network traffic and it is something I would look into if you plan to expose any of your services to the internet. Usually when you start with Docker, you probably would just expose Ports from the Containers, which get mapped to the IP of your host... and so all those Containers will have access to your LAN. At least try to separate that.

    The next thing I wanted to do, is run my Containers rootless, which means that no container has root permissions if in case something within the container decides to let the docker service do something malicious on the host, it should not be able to run as root. The caveat here is, that docker does not support VLANs in rootless mode. I spend half a day converting everything to Podman, because people where praising podman left and right if you want to run rootless, but then I found out that Podman does not support VLANs in rootless mode either :->

    Using VMs as described above would make the "I can not use docker rootless" problem less of a problem, but I decided against VMs because of Resources / Budget.

    What I can recommend when you start, do not try to make things too complicated until you are familiar with Docker and understand what you are doing. As you get better, you might want more and learn more stuff as you go.

    You could just install a Linux Distribution you are familiar with (I use Ubuntu Server LTS 22), install Docker and just play around with it a bit to see how everyting works. Only start exposing Services to the Internet if you know what you are doing.

    Maybe a few tips or keywords for you of stuff I went through step by step for later usage.

    • If you expose Services to the Internet, use a Reverse Proxy you think you will understand (NGINX, Traefik, Caddy...)
    • Try to segment your network if your Hard- / Software allows it to separate LAN Services from Services exposed in the Internet
    • Start documenting your setup from the beginning! If you are like me, everything is clear as you do it... but when I come back a month later I wonder how I set up the VLANs or what each Environment Setting does for a specific container etc ;-)
    • Instead of using Docker Volumes, think about redirecting Container directories to directories on the host instead. All my containers have their data under /opt/

      <container>

      and all my docker-compose files are in another, separate directory.
    • Implement a Backup solution early on (I use kopia, which backs up my compose directory and /opt, which should be everything I need to set up everything again on a new host)
    • Once you have a few containers up and running and think you are familiar how they work, start use docker-compose. Having a compose file for each container makes updating and maintaining them super easy. There is an updated image for a container? Just run docker-compose up -d and you are done. You need a variation of a container for testing? Copy the compose file, make adjustments and run it.
    • I use watchtower to automatically check if new docker images are available. I use it in monitoring mode. It will check and download for new images, but will not restart the containers. Instead I receive an E-Mail from watchtower. I can then check if the update is for a container exposed to the internet and then will let kopia do another backup run and just do a docker-compose up -d to restart / update the respective container, check if it still does what it does and am done.
    • Did I mention that you should document everything you do? If you are like me and have a memory like an earthworm, you should document your setup from the beginning ;-)

    All in all: Do not rush it, do not feel the pressure to do everything I wrote. You might even come up with other, much better fitting solutions for you than what I or others here are doing. The most important things? Have fun and think twice what and how you expose a service to the public :-)