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

  • netburnrEnglish
    2•2 years ago

    You can’t have the checkbox for federation and private, the server will crash and tell you that in the lemmy log. Had that happen when I did thy to setup without email the first time.

    • @[email protected]English
      3•2 years ago

      Private and federation are mutually exclusive concepts. Private instances are ones that intentionally don’t federate - like a private company community that’s locked to their intranet. For self hosted Lemmy instances you just need to close registration. Then since no one can apply, the only use case for email becomes the Forgot Password button for if you forget your password and at that point you’re better served with a password manager.

    • ubergeek77OPEnglish
      1•2 years ago

      “Private instance” and “disable registration” are not the same thing. There are separate options for both. It is possible to run a federated single-user instance with registrations disabled. That’s how I run mine.

    • 8565English
      1•2 years ago

      Weird. I used this script with no working email. How’s it going from my private instance that is federated?