How do I build up a lemmy instance right from the scratch ?
from Docker@lemmy.world to selfhosted@lemmy.world on 03 May 12:49
https://lemmy.world/post/29079873

#selfhosted

threaded - newest

arotrios@lemmy.world on 03 May 12:54 next collapse

Haven’t done it myself yet, but here’s the docker install guide… seeing what your username is and all…

user224@lemmy.sdf.org on 03 May 13:16 next collapse

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.

Docker@lemmy.world on 03 May 20:02 collapse

I took this name because I thought that Docker is a fanciful name😳😳😳

rasbora@lemm.ee on 05 May 01:19 collapse
mesamunefire@piefed.social on 03 May 14:12 next collapse

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.

asudox@lemmy.asudox.dev on 03 May 15:36 next collapse

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.

bdonvr@thelemmy.club on 03 May 15:56 next collapse

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

BlueEther@no.lastname.nz on 03 May 16:54 next collapse

github.com/ubergeek77/Lemmy-Easy-Deploy

Is very easy, by @ubergeek77@lemmy.ubergeek77.chat. Not sure if they are doing more updates though?

ubergeek77@lemmy.ubergeek77.chat on 03 May 17:43 collapse

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:

github.com/LemmyNet/…/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 :)

BlueEther@no.lastname.nz on 03 May 18:37 collapse

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

ubergeek77@lemmy.ubergeek77.chat on 03 May 19:14 collapse

What issue did you have? If I can handle it for the user automatically, I can add a best effort attempt to avoid it.

BlueEther@no.lastname.nz on 03 May 19:37 collapse

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/certmagic@v0.21.6/solvers.go:386:9: invalid composite literal type libdns.Record 

68.67 /go/pkg/mod/github.com/caddyserver/certmagic@v0.21.6/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/certmagic@v0.21.6/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`

ubergeek77@lemmy.ubergeek77.chat on 03 May 20:05 collapse

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 :/

vegetaaaaaaa@lemmy.world on 04 May 17:03 collapse

RTFM join-lemmy.org/docs/…/administration.html

Agent641@lemmy.world on 04 May 21:33 collapse

What distro do you use?

vegetaaaaaaa@lemmy.world on 05 May 04:04 collapse

Debian