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

  • falcon15500@lemmy.nine-hells.net
    link
    fedilink
    English
    arrow-up
    1
    ·
    1年前

    I am not 100% surprised they refuse to do it for new accounts. If you have an account that has been with them for a while, they most likely would open it.

    Problem with SES is that you start sandboxed and can only deliver to specific email addresses - which obviously won’t work here.

    • Zach @bigfoot.ninja
      link
      fedilink
      English
      arrow-up
      2
      ·
      1年前

      Yeah maybe, i’ve had my account for a few years but who knows.

      If i decide do use email i’ll just make an smtp mail server on my homelab