• 4 Posts
  • 127 Comments
Joined 1 year ago
cake
Cake day: February 8th, 2025

help-circle










  • Just throw your services in a docker-compose.yml file, create a docker bridge network, and assign the:

    networks:
        - YourDockerNetwork
    

    To the services in the yaml file, specify the ports it want’s to open with

    ports:
        - 8080:8080
    

    And let it start up. If you want to get more complicated suggest reading the man page which really isn’t that long of a read.

    Networking really cannot be simplified, you have to view it in a logistical way of how is Point A communicating with Point B which where Docker bridge networks come into play, they make the communication easy, if all your containers are all on the same docker network all you have to do is specify http://ContainerName:Port for them to communicate back and forth internally.


  • The other thing I tried was deploying an Element server so they could talk to family on their own without risk of exposure to the world at large, but ended up abandoning this.

    Matrix is a PIA to configure properly, it is nice to have once you got it running but you’ll end up spinning like 8 different services (if you use Docker) for all the functionality to work.


  • Additionally, I recommend unbound for those already on pi-hole.

    Never could get unbound to work properly, it would always knock my internet out to the point of troubleshooting for hours, whether that be Pi-Hole, OpenSense or Technitium I’ve always had issues with unbound.

    As much as I like hosting my own services, I want them to be reliable.