this post was submitted on 10 Jun 2023
15 points (100.0% liked)

Self Hosted - Self-hosting your services.

506 readers
1 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

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Cross-posting

If you see a rule-breaker please DM the mods!

founded 3 years ago
MODERATORS
 

I've been working with the two suggested LemmyNet installation methods; Docker and Ansible. Neither are too wild of a setup, but they aren't plug and play docker-compose-like, either.

I want to run a LemmyNet on a subdomain; lemmy.domain.com, and use nginx-proxy-manager to point traffic in the right direction, but it will be on the same local IP... some port changes will need to be made.

Is anyone running their own instances? Have suggestions or tips with things that helped you lean up a lemmy.subnet?

Cheers!!

  • pAULIE42o
  • . . . . . . . . . . .
  • /s
top 13 comments
sorted by: hot top controversial new old
[–] don@lemmy.donmcgin.com 6 points 1 year ago

Hey, take a look at this user's post, they set up their instance with docker and posted their compose and config files. I was able to get up and running using that.

[–] slashzero@hakbox.social 4 points 1 year ago

I am fairly sure you can customize the nginx.conf that is bundled with the docker installation method, to add some virtual host directives to add any subdomains you want and forward to the appropriate backend.

You could also run another nginx instance on your host to handle all the subdomain virtual hosts and forward to the lemmy containers. It’s a bit more complicated but definitely should be possible. You will have to do the research and figure it out via trial and error though, unfortunately. Not a lot of documentation and how-to articles out there yet. This is all still fairly new, relatively speaking.


Note: posted using mlem for iOS, sorry if this comment is messed up in any way.

[–] grouvie@lemmy.help 3 points 1 year ago (1 children)

I am running Lemmy in a Kubernetes cluster. You can find the helm charts and a short documentation here: https://github.com/grouvie/lemmy_help

I am happy to help should anyone have further questions. :)

[–] ultraHQ@lemmy.one 1 points 1 year ago* (last edited 1 year ago) (1 children)

Interesting! What are the specs of the pods in your cluster?

[–] grouvie@lemmy.help 2 points 1 year ago* (last edited 1 year ago)

Hosting at Hetzner.

  • 3x CX41 -> 4 vCPU, 16GB RAM
  • 3x CX21 -> 2 vCPU, 4GB RAM
  • 1x CPX21 -> 3 vCPU, 4GB RAM

Server configuration may appear a bit weird. I have the storage managed with longhorn. It's not on the nodes, but mounted to them.

[–] mrmanager@lemmy.today 3 points 1 year ago* (last edited 1 year ago)

I have not done this exactly but I recommend Treafik for setting up a reverse proxy. The reason I like it is because it's quite simple and visual.

You have three things. Entrypoints (listeners on a port), Routers (rules for how traffic should go) and Services (your stuff, like Lemmy).

https://traefik.io/traefik/

The visual part is quite nice. And you route traffic using ordinary docker labels if you use docker for example.

[–] alvaro@social.graves.cl 1 points 1 year ago (2 children)

@paulie420@beehaw.org any idea if it is worth to have lemmy installed if you are already using another fediverse client?

[–] alvaro@social.graves.cl 1 points 1 year ago

@paulie420@beehaw.org Apparently that is the case!

[–] alvaro@social.graves.cl 1 points 1 year ago

@paulie420@beehaw.org Apparently you can use other fediverse clients to post as well!

[–] wizjenkins@lemmy.wizjenkins.com 1 points 1 year ago (1 children)

I host my instance exactly like this with Nginx Proxy Manager. Here's my config:

  • Block Common Exploits and Websockets Support - on
  • Add a custom location with the following settings:
    • proxy_set_header X-Real-IP $remote_addr;
    • proxy_set_header X-Forwarded-For $remote_addr;
    • proxy_set_header X-Forwarded-Host $remote_addr;
    • real_ip_header X-Real-IP;
    • real_ip_recursive on;
  • for SSL turn on HTTP/2 Support

I had to add the custom config so that I would get the IP address of the clients and federated servers. Otherwise I was hitting rate limits on the Lemmy server.

[–] paulie420 1 points 1 year ago

Ahh; these settings are interesting... I turned on 'block common exploits', but HTTP/2 support might be smart, too... yer custom location stuff is above my head, but you've got me sniffing a bit now. :P

[–] mark@social.cool110.xyz 1 points 1 year ago (1 children)

@paulie420 Don't forget that there are alternatives out there that are (almost) fully compatible, I'm just using my #Friendica instance that I set up years ago.

[–] paulie420 2 points 1 year ago

Ok; I'll take a peek... but I'm really feeling the LemmyNet vibe. That being said, I haven't used friendica so I'll drop by and have a l00k.

load more comments
view more: next ›