• ubergeek77@lemmy.ubergeek77.chatEnglish
      101·
      14 hours 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:

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

      • BlueÆther@no.lastname.nzEnglish
        11·
        13 hours 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

          • BlueÆther@no.lastname.nzEnglish
            11·
            12 hours ago

            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.chatEnglish
              11·
              12 hours 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 :/