Selfhosted

54534 readers

637 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.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

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

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Hosting multiple services with one IP address. (piefed.social)

submitted 1 day ago by a_person@piefed.social to c/selfhosted@lemmy.world

27 comments fedilink hide all child comments

Hello people, I recently rented a vps server from OVH and I want to start hosting my own piefed instance and a couple other services. I am running debian 13 with docker, and I have nginx proxy manager almost set up. I want to set up subdomains so when I do social.my.domain it will go to my piefed instance, but how do I tell the machine to send piefed traffic to this subdomain and joplin traffic (for example) to another domain? Can I use nginx/docker natively for that or do I have to install another program. Thanks for the advice.

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

[–] just_another_person@lemmy.world 11 points 1 day ago* (last edited 1 day ago) (1 children)

I'll be honest with you here, Nginx kind of ate httpd's lunch 15 years ago, and with good reason.

It's not that httpd is "bad", or not useful, or anything like that. It's that it's not as efficient and fast.

The Apache DID try to address this awhile back, but it was too late. All the better features of nginx just kinda did httpd in IMO.

Apache is fine, it's easy to learn, there's a ton of docs around for it, but a massively diminished userbase, meaning less up to date information for new users to find in forums in the like.

[–] Black616Angel@discuss.tchncs.de 1 points 1 day ago

Apache has the better open source tooling IMO.

I use both, but at work I prefer apache simply for its relative ease of setting up our SSO solution. There is probably a tool for that in nginx as well, but its either proprietary or hard to find (and I did try to find it, but setting up and learning apache and then SSO was actually easier for me).