this post was submitted on 20 Jun 2023
6 points (100.0% liked)

Asklemmy

43402 readers
855 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago
MODERATORS
 

Slowly exploring the lemmy ecosystem, since I don't want to use reddit, and was wondering if selfhosting would be a good idea?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 1 year ago (1 children)

Many of the parts can be swapped out for alternatives, shared with other services

Let’s go through it.

  1. proxy: image: nginx:1-alpine I already have one running, why do I now need another one installed als another container exclusively for Lemmy?
  2. pictrs: image: asonix/pictrs:0.4.0-beta.19 I have no other use for this except for Lemmy, why do I need another container just for this application I never heard of?
  3. postgres: image: postgres:15-alpine I have absolutely no use for Postgres. Why do I need to install a database server as container just for being used by Lemmy, and Lemmy only?

And then, yes, of course, lemmy and lemmy-ui

So 5 different containers (and 4 volumes, and 2 networks) all set up only for Lemmy, cluttering my setup – not counted in all the volumes, containers, and networks set up by the 3 additional containers.

And since I’m pinned to specific versions I need to manually check new/changed dependencies when updating Lemmy instead of just rebuilding the container.

I still see no point in that.

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

It is common to run more than one application in a given server. Nginx, for example, is widely used as a reverse proxy and web server for operating multiple containerized applications on the same server. Postgres is a commonly used database that can potentially be used on hundreds of applications simultaneously. Duplicating them on all containers would just create a mountain of problems and waste resources for no real benefit.

If all you’re running is lemmy then why are you so upset about containers “cluttering” up things? What is there to clutter up, your docker ps output ? If you want, just pretend the host is itself a container running lemmy (which it might just be, depending on your host!). Alternately, make your own nested container that just does a docker-compose up and pointlessly duplicate all the services you want. Complaining that the container managers don’t do this for you, to the detriment of others who don’t share your specific niche, is just blatantly entitled and absurd.

[–] [email protected] 1 points 1 year ago (1 children)

Nginx, for example, is widely used as a reverse proxy

I use it as reverse proxy already. Why do I need to install a reverse proxy for Lemmy?

If all you’re running is lemmy then why are you so upset about containers “cluttering” up things?

That’s the thing: i don’t.

But maybe I should get a real or virtual machine used exclusively for Lemmy and adding its Docker environment to my current Portainer installation.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

I use it as reverse proxy already. Why do I need to install a reverse proxy for Lemmy?

You don't. Configure the one you already have and just remove that entry from your docker-compose. This is exactly why they're handled as separate containers.

[–] [email protected] 1 points 1 year ago

And by “configuring” you mean nothing more than simply setting up the connection from example.com:443 to the machine and exposed port? That would at least solve 1 out of 5 issues I have … :)