In the past few days, I’ve seen a number of people having trouble getting Lemmy set up on their own servers. That motivated me to create Lemmy-Easy-Deploy, a dead-simple solution to deploying Lemmy using Docker Compose under the hood.

To accommodate people new to Docker or self hosting, I’ve made it as simple as I possibly could. Edit the config file to specify your domain, then run the script. That’s it! No manual configuration is needed. Your self hosted Lemmy instance will be up and running in about a minute or less. Everything is taken care of for you. Random passwords are created for Lemmy’s microservices, and HTTPS is handled automatically by Caddy.

Updates are automatic too! Run the script again to detect and deploy updates to Lemmy automatically.

If you are an advanced user, plenty of config options are available. You can set this to compile Lemmy from source if you want, which is useful for trying out Release Candidate versions. You can also specify a Cloudflare API token, and if you do, HTTPS certificates will use the DNS challenge instead. This is helpful for Cloudflare proxy users, who can have issues with HTTPS certificates sometimes.

Try it out and let me know what you think!

https://github.com/ubergeek77/Lemmy-Easy-Deploy

  • @Declared0978English
    2•1 year ago

    So stupid question - how do you shut them down? Docker compose down or stop don’t seem to work.

    Also, as an intermediate (spoiled Unraid) user, if I’m behind nginx proxy manager with custom ports do I just change 80 and 443 in the lemmy docker-compose? I’m doing this in a Debian VM.

    • ubergeek77OPEnglish
      2•1 year ago

      I’ll add some better instructions for this to the readme.

      You can do any Docker compose commands by changing to the ./live folder, then running:

      docker compose -p lemmy-easy-deploy <command>

      <command> can be whatever Docker Compose supports, up,down,ps, etc.

      I don’t have config options for the ports, but you can just change them in docker-compose.yml.template to change what they’re listening on. As long as yourdomain.com:80 is reachable from the public, it shouldn’t matter what routing shenanigans are going on behind it.