Selfhosted

60210 readers

951 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.

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

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

submitted 5 months 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 5 months ago* (last edited 5 months 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 5 months 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).