1.2.7

• New feature: Advanced Customization
  • Every template of Lemmy-Easy-Deploy can now be overridden easily.
  • It is now possible to run pre- and post-deployment scripts.
  • These will make it easier to maintain custom deployments without modifying git-tracked files.
    • Example: You can now essentially "inject" things like Ntfy into the deployment (although configuration is still very manual)
  • This feature is for advanced users only!*
• Made updater more reliable by force-pulling tags from this repo
• Improved README
• Improved user prompts and script output
• Fixed an oversight in how the email block of lemmy.hjson is generated

1.2.6

• General compatibility fixes; should be more reliable on more *nix systems
  • Some non-POSIX checks were replaced with POSIX compliant code
  • The script will explicitly warn you if required binaries are missing
  • The --diag output has been improved to not assume certain binaries are available
• #!/usr/bin/env bash is now used for better portability if bash is not at exactly /bin/bash
• More warnings were added:
  • Warn if not using bash
  • Warn if not running on Linux
  • Inform users that managing the stack directly is not advised
  • Split out Docker/Docker Compose warnings; change check to support Docker >20

1.2.5

• Added a warning about an issue that occurs when the Docker host's hostname is identical to Lemmy's hostname
• Formatting improvements

1.2.4

• Improve warning messages
• Allow a Github API token to be used for version checks (optional)
• Fix running compose down on redeploys

1.2.3

• Fixed an issue where the current version of Docker may not be detected properly

• Custom environment variables are now supported by each service. Please create the respective files in order to use them:

  • *Note: these paths are relative to deploy.sh. Do not place these in ./live
  • ./custom/customCaddy.env
  • ./custom/customLemmy.env
  • ./custom/customLemmy-ui.env
  • ./custom/customPictrs.env
  • ./custom/customPostgres.env
  • ./custom/customPostfix.env
  • These files are environment files. In general, they follow the syntax VARIABLE=VALUE. For more info, please see the official Docker docs for the syntax of these files:
    • https://docs.docker.com/compose/environment-variables/env-file/

• You may now supply a customPostgresql.conf file to your Postgres container. Copy it here in order to use it:

  • *Note: this path is relative to deploy.sh. Do not place this file in ./live
  • ./custom/customPostgresql.conf
  • This will be mounted over /etc/postgresql.conf in the Postgres container.

• Improvements have been made to the first-time setup experience to reduce confusion for new users

1.2.2

• Docker <24 compatibility
• Warning about unsupported Docker versions
  • Future incompatibilities may not be fixed, please use official Docker versions!

1.2.1

• Hotfix for a small error when re-upping
• Formatting improvements

1.2.0

• Support Lemmy 0.18.x
• Added warning about updates being one-way
  • I think we all learned our lesson with all the 0.18.0 bugs
• Default to multiarch images built by me, fixes ARM issues: https://github.com/ubergeek77/lemmy-docker-multiarch
• More settings in config.env.example, including custom SMTP settings (external email servers can now be used)
  • Removed BUILD_FROM_SOURCE, source builds are now created by prefixing a tag/commit with git:
• Implement a better self-updater
• More diagnostic info for me to help people
• Track Backend and Frontend versions separately
• New command line options (NOTE: -u has changed, please see the readme!)
  • Option to shutdown the current deployment
  • Options to specify the Lemmy Backend and Frontend tags separately
  • Option to rebuild a local source build without resetting the git tree, useful if running custom Lemmy patches
• Stopped deployments will now automatically re-start if deploy.sh is run and there were no updates.

1.1.4

For the safety of everyone's servers, I am disabling updates to any 0.18-adjacent build. If you are an advanced user, you can remove my block if you want, but I will not be supporting any 0.18.0-related issues until Lemmy fixes their issues.

My own server is broken because of 0.18.0, so I feel it is safer to just block 0.18.0 updates for now. Hopefully this saves people some headache.

Keep an eye on these issues:

LemmyNet/lemmy#3296

LemmyNet/lemmy-ui#1530

1.1.3

Publishing this release just to show people the warning banner. 0.18 is very buggy. I regret updating my own server...