Selfhosted

60810 readers

959 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

ExposeMap: a small CLI to map what a Docker Compose file appears to expose (lemmy.world)

submitted 1 month ago by kaibuild@lemmy.world to c/selfhosted@lemmy.world

4 comments fedilink hide all child comments

I wanted a quick local way to review my own Docker Compose stacks before assuming a service was private, behind a reverse proxy, or only bound to localhost.

ExposeMap is a small open-source CLI that reads a docker-compose.yml file and reports exposure hints: internal, localhost-only, directly exposed from Compose config, reverse-proxy exposed, or unknown.

It generates a Markdown report and Mermaid diagram. It checks common port mappings, localhost bindings, Traefik-style labels, likely reverse proxy services, and risky directly published database/admin ports.

Important limitation: it does not prove internet reachability, run network scans, connect to containers, modify Compose files, inspect secrets, or upload anything.

GitHub: https://github.com/kaibuild/exposemap

I'm especially looking for sanitized Compose edge cases where the classification is misleading or the wording should be clearer.

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

[–] clmbmb@lemmy.dbzer0.com 19 points 1 month ago (1 children)

I don't get why people don't try to use other languages for these type of CLI tools. I get that they are familiar with JavaScript, but npm is a nightmare right now and I wouldn't install anything with it for some time.

There's always shell scripting available, also Go, Rust and lots of other options (I specifically don't mention Python, as pip is also a bit problematic).

[–] lastweakness@lemmy.world 1 points 1 month ago

How is Rust not problematic? Cargo has the same risks involved afaik