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:
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.
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 :/
https://github.com/ubergeek77/Lemmy-Easy-Deploy
Is very easy, by @ubergeek77@lemmy.ubergeek77.chat. 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:
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 :/