Selfhosted

40200 readers

645 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]

NPM - What services need what toggled? (slrpnk.net)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

Hiya, just got NPM installed and working, very happy to finally have SSL certs on all of my serivces and proper URLs to navigate to them, what a breeze! However, as I am still in the learning process: I am curious to know when to enable these three toggles and for what services. I assume the "Block Common Exploits", can always be turned on. But unsure about the two others. Some applications have not worked until I turned on the Websockets Support, but I dont really know what it does, nor do I know what applications need this in order to fully work. Are there any thumb rules for these things?

Appriciate any pointers! 🌻

top 9 comments

sorted by: hot top controversial new old

[–] [email protected] 0 points 7 months ago (1 children)

That's not NPM, that's Nginx proxy manager. They are very much not the same thing.

[–] [email protected] 0 points 7 months ago (1 children)

I've seen others calm this npm, so went along and did the same 🙃

[–] [email protected] 0 points 7 months ago (1 children)

It’s even abbreviated that way in the official documentation: https://nginxproxymanager.com/advanced-config/

[–] [email protected] -1 points 7 months ago (2 children)

Two wrongs don't make a right. I was scratching my head for a few seconds looking at the thumbnail and the title. And even the post body didn't clarify things. 🤷🏻

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

Multiple things have the same abbreviation, it's really all about the context it's used it imo. Considering Ngninx Proxy Manager being a very well known tool in the selfhosters toolbelt, I figured it would be familiar enough to use.

[–] [email protected] 1 points 7 months ago

You also have a screenshot from proxy manager so any confusion should have been short lived

[–] [email protected] -1 points 7 months ago* (last edited 7 months ago)

Yeah I had literally no idea what you were talking about until you mentioned the actual name in the comments.

NPM almost universally refers to node package manager in any developer or development adjacent conversation in my experience. Given that both the site, the command, the logo, and the binaries are "npm" makes that more appropriate.

Nginix proxy manager is far to niche to be referred to universally by acronym when it's only ever used as an acronym when the context for it's usage has already been defined (ie. In it's documentation).

This becomes much more clear when you Google the acronym.

[–] [email protected] 0 points 7 months ago (1 children)

Is it wrong to abbreviate your own product in your documentation?

[–] [email protected] -1 points 7 months ago

Their own doc, sure why not.

Any other context where there's a giant with the same name. No, please at least write it out expanded once.