You must log in or # to comment.
Haven’t done it myself yet, but here’s the docker install guide… seeing what your username is and all…
https://github.com/ubergeek77/Lemmy-Easy-Deploy
Is very easy, by @[email protected]. Not sure if they are doing more updates though?
Hi!
The project is still active! I just haven’t needed to develop any updates because it’s currently stable, and the upstream Docker compose template, which is a reference for my project, hasn’t changed in 9 months:
https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/docker-compose.yml
Whenever Lemmy releases a new Docker container, it will just pull the latest one automatically. This will continue to be compatible indefinitely until the compose deployment (linked above) has any breaking changes added to it that I need to incorporate.
Thank you for the shout out :)
I did have a slight issue when I went to 0.19.11 with caddy cloudflair, but that is outside of the bounds of what you control
What issue did you have? If I can handle it for the user automatically, I can add a best effort attempt to avoid it.
Just a build conflict, it was resolved upstream in a day or so:
[proxy builder 2/2] RUN xcaddy build --with github.com/caddy-dns/cloudflare:
…
3.16 go: downloading github.com/googleapis/enterprise-certificate-proxy v0.3.2
53.19 go: downloading github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da
53.47 2025/04/10 07:47:10 [INFO] exec (timeout=0s): /usr/local/go/bin/go build -o /usr/bin/caddy -ldflags -w -s -trimpath -tags nobadger,nomysql,nopgx
68.67 # github.com/caddyserver/certmagic
68.67 /go/pkg/mod/github.com/caddyserver/[email protected]/solvers.go:386:9: invalid composite literal type libdns.Record
68.67 /go/pkg/mod/github.com/caddyserver/[email protected]/solvers.go:445:17: zrec.record.Type undefined (type libdns.Record has no field or method Type)
68.67 /go/pkg/mod/github.com/caddyserver/[email protected]/solvers.go:449:45: zrec.record.Name undefined (type libdns.Record has no field or method Name)
88.82 2025/04/10 07:47:45 [INFO] Skipping cleanup as requested; leaving folder intact: /tmp/buildenv_2025-04-10-0746.3854595282
88.82 2025/04/10 07:47:45 [FATAL] exit status 1
failed to solve: process “/bin/sh -c xcaddy build --with github.com/caddy-dns/cloudflare” did not complete successfully: exit code: 1`Ah I see. I’ve gotten into some back and forth with the maintainer of Caddy about these build inconsistencies and lack of versioning, and he responded by locking issues on me… twice.
After that communication, I resigned to just keep things as they are because upstream is not willing to make the experience better for use cases like these.
He is impossible to work with, but Caddy is just really good :/
I’ve done it twice. Easiest is using yunohost, second is using their docker container. Both require a bit of a sysafmin background for anything with more than 10 users, at least right now.
The times I did it, I went through their official documentation and their Docker files.
Sorry, no useful reply. I just want to check on the post later. But I don’t even know to use docker… Heh, just noticed your username is Docker.
I took this name because I thought that Docker is a fanciful name😳😳😳
First question is - are you familiar with Linux command line at all? If not get familiar with it first.
Second you’ll need to own or buy a domain and point it to the server’s IP.
Then install either Ubuntu Server or Debian on the server, setup SSH and run this Ansible project - https://github.com/LemmyNet/lemmy-ansible
If that’s not comprehensible to you, I’d really recommend getting more familiar with Linux command line and servers before I’d recommend starting a Lemmy instance.
I used podman. Though you probably can use Ansible, if you want it simple.
There are also a few container management UIs like yunohost that let you deploy Lemmy with a click, but last I checked, it used a very outdated version of Lemmy. There’s also elest.io.
