1.4.3

Deploy caddy before deploying lemmy-ui

This might work around issues people have been having with lemmy-ui, as it seems to just give up on the SSR if it can't reach the instance via the public domain name

1.4.2

1.4.2 - hotfix for 1.4.0 / 1.4.1

There was a misplaced space that caused a warning message to be erroneously written as an empty file with the name 2 ! such as credentials or IP addresses. This is not a critical update, just something I wanted to get a fix out for.

1.4.1 hotfix notes:

I forgot to update the lemmy.hjson template, since the Pictrs API key variable changed names. This would have caused an API key mismatch, so anything requiring authentication to the Pictrs API would have broken. I didn't catch this at first, and my instance still seemed to generate and store post thumbnails properly before I did, so you may not need this hotfix immediately if you want to avoid downtime.

1.4.0 patch notes:

This release adds support for Lemmy 0.19.4 and higher.

As Lemmy 0.19.4 requires a major Postgres version bump, which in turn requires a database migration, Lemmy-Easy-Deploy has switched to using pgautoupgrade as the Postgres container. This will quickly and easily change any existing databases over to the Postgres 16 format:

https://github.com/pgautoupgrade/docker-pgautoupgrade

This is a major semver bump, because the behavior on deployment health checks has changed slightly. Now, there is no time limit for deployments, and the user is provided the option to CTRL+C to cancel a deployment. The removal of the time limit is to allow for any database migrations enough time to run.

Huge thanks to everyone who helped test, and for pallebone for suggesting pgautoupgrade - huge lifesaver!

If you have any issues with your deployments, please feel free to file an issue!

1.4.0

This release adds support for Lemmy 0.19.4 and higher.

As Lemmy 0.19.4 requires a major Postgres version bump, which in turn requires a database migration, Lemmy-Easy-Deploy has switched to using pgautoupgrade as the Postgres container. This will quickly and easily change any existing databases over to the Postgres 16 format:

https://github.com/pgautoupgrade/docker-pgautoupgrade

This is a major semver bump, because the behavior on deployment health checks has changed slightly. Now, there is no time limit for deployments, and the user is provided the option to CTRL+C to cancel a deployment. The removal of the time limit is to allow for any database migrations enough time to run.

Huge thanks to everyone who helped test, and for pallebone for suggesting pgautoupgrade - huge lifesaver!

If you have any issues with your deployments, please feel free to file an issue!

1.3.4

This release disables deployments for 0.19.4 and higher, and forces the use of 0.19.3 if it is detected.

I am testing a version compatible with 0.19.4, please see below for updates:

#91

1.3.3

Update pictrs in template file to 0.4.7

1.3.2

Fix some minor issues, add theme support, tested and working with 0.19

1.3.1

• Caddy has resolved upstream packaging issues, remove version locks on Caddy

1.3.0

• Locks Caddy to version 2.7.2, avoids build issues caused by versioning discrepancies in upstream Caddy/Cloudflare plugin

1.2.9

• One line change to use the correct path for postgresql.conf
  • Only needed if specifying a customPostgresql.conf file

1.2.8

• Bumped Pictrs version to 0.4

No major changes in this release, the container used for pictrs was changed to version 0.4 to now match the upstream version.

Pictrs 0.4 adds support for Object Storage. I cannot support/help people using Object Storage, but the only needed change is extra environment variables for Pictrs. You can define those environment variables in Lemmy-Easy-Deploy using the customPictrs.env file as outlined in Advanced Configuration.