Selfhosted

40219 readers

1596 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Need help: accessing all my containers by name (yall.theatl.social)

submitted 1 year ago by [email protected] to c/[email protected]

34 comments fedilink hide all child comments

I’m to the point now where my little home device has enough services and such that bookmarking them all as http://nas-address:port is annoying me. I’ve got 3 docker stacks going on (I think) and 2 networks on my Synology. What’s the best or easiest way to be able to reach them by e.g. http://pi-hole and such?

I’m running all on a Synology 920+ behind a modem/router from my ISP so everything is on 192.168.1.0/24 subnet, and I’ve got Tailscale on it with it as an exit node if that helps.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 1 year ago (2 children)

There's a few options. Personally I use nginx. You can build a proxy container running nginx, then you can direct traffic to other containers.

I do things like serviceX.my.domain and that will know to proxy traffic to serviceX. Added benefit is that now you have one ingress to your containers, you don't need to memorize all of those ports.

I know traefik is a thing that other people like

If you want something real simple you could also do Heimdall, which let's you register your systems you have running, you open Heimdall first and it'll direct you to what you have running, but that's essentially just fancy bookmarks

[–] [email protected] 2 points 1 year ago (1 children)

I looked at Heimdall and came to the same conclusion, I could just whip up a static html page of links, or make bookmarks, easier than maintaining another docker.

[–] [email protected] 1 points 1 year ago

Yep, tried it and yeah just a fancy page for bookmarks - although it did make a nice home/landing page for me whenever I opened a new tab.

Nginx is your friend then, set up a good proxy and it'll be much easier to navigate your network.