Self Hosted - Self-hosting your services.

11447 readers

2 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

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

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!

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.

Cross-posting

[email protected] is allowed!
[email protected] is allowed!
[email protected] is allowed!
[email protected] is allowed if topic has to do with selfhosting.
[email protected] is allowed!

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

founded 3 years ago

MODERATORS

[email protected]

[Project] Lemmy EZ-Mode Docker-Compose Stack (github.com)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

I made this stack based on my own deployment of Lemmy, it should allow anyone to run a Lemmy stack in Compose, with LE SSL behind Traefik. I've tested it behind docker-compose on Windows and Ubuntu. Interested in any feedback or PRs :)

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

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

6 Containers for one application … And I thought the original Docker setup was annoying. Why include SSL stuff and a reverse proxy? I am pretty sure most people already have that set up.

Edit:

Just checked the readme in detail. They suggest rm -R’ing the Docker volumes directory to, I quote, “rm any persistent volumes”. Also manually messing with upstream data before manually creating the image again.

I don’t see how this is any better than the original mess. It just adds more containers to the stack and gives very questionable advices.

An “EZ-mode” for me would be one image containing all the relevant Lemmy-specific software (lemmy, lemmy_ui pictrs and maybe even the database) and needing one volume mapped to one path in the container.

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

Maybe for people who only want to host lemmy and nothing else

load more comments (2 replies)