Comment

Comment on How do I build up a lemmy instance right from the scratch ?

ubergeek77@lemmy.ubergeek77.chat ⁨1⁩ ⁨week⁩ ago

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

source

Sort:hotnew top

BlueEther@no.lastname.nz ⁨1⁩ ⁨week⁩ ago
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

source
- ubergeek77@lemmy.ubergeek77.chat ⁨1⁩ ⁨week⁩ ago
  What issue did you have? If I can handle it for the user automatically, I can add a best effort attempt to avoid it.
  
  source
  - BlueEther@no.lastname.nz ⁨1⁩ ⁨week⁩ ago
    Just a build conflict
    
    [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`
    
    source
    ubergeek77@lemmy.ubergeek77.chat ⁨1⁩ ⁨week⁩ ago
    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 :/
    
    source