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

  • JCreazy@midwest.social
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    I will definitely try this out. I already have my domain and SSL certificate. This will work on linode right?

    • ubergeek77@lemmy.ubergeek77.chatOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      It will work on pretty much anything that has a public IP and a domain pointing to that IP. The only thing that won’t work “out of the box” for most users is email, as most VPS providers block port 25. If you’ve requested access to port 25 and have been approved to use it, you can edit config.env to turn on the email service.

      As for your SSL certificate, unfortunately this does not support importing your own certificate. It’s made for beginners, after all :p

      But there should be no problems with Caddy simply requesting a new one for you!

          • JCreazy@midwest.social
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            Once I got it up and running, I had to figure out how to get my domain to redirect to it. Now I just gave to figure out how to start federating with other instances.

            • ubergeek77@lemmy.ubergeek77.chatOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              If your instance is fully reachable from the public, all you have to do is search for the community you want to federate with in your search bar. For example, if you wanted to federate with and subscribe to this community, put this in your search bar, then hit search:

              https://lemmy.world/c/selfhosted
              

              It works for kbin communities too!

              You might see some people say to search it like !selfhosted@lemmy.world, but I have way more success with doing it like that. After you’ve done that, you can click on Communities at the top of your instance’s page, click the All tab, then start subscribing with some of them.

              It will only start pulling “new” data though, you won’t get days or week old posts like this. But, if there is something you want to see/comment on from your instance, you can put the direct link to any post, comment, or user into your instance’s search bar, to make it “aware” of that post/comment/user. Then you can just interact like normal.

              Welcome to the self-hosted Fediverse!

        • ubergeek77@lemmy.ubergeek77.chatOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          I’m not sure what you mean? Most people are just self hosting instances for themselves, where email isn’t needed. My instance doesn’t have an email service.

          And as I explained, if email is something you want, I support this, and I give you an easy option to turn it on. It’s not the default because there is not a public VPS host out there that lets you use port 25 without special approval.

          • netburnr@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            Email config is needed for lost passwords. It’s also needed for account verification, if you run without verification you could easily become a place for people to abuse other servers and get yourself defederated.

            Many web hosts have poisoned mail IPs, so setting up with a smtp config to a well known site server is required if you want your emails to be delivered.

            • ubergeek77@lemmy.ubergeek77.chatOP
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              1 year ago

              And that is why I don’t advertise this as supporting email out of the box, and why it’s an advanced option without any support from me. The embedded postfix server is part of the official Docker Compose deployment from upstream Lemmy, and it’s part of the officially supported Ansible deployment too. Those deployment methods are what this is modeled after. That is as far as I go on email support. If upstream Lemmy started including some automatic AWS SNS configuration, I would adopt it, but they have not done so.

              Everyone who has reported success to me so far are running single user instances for themselves. That is my target audience, and for that audience (and myself), email is not even close to being a hard requirement.

              However, if you would like to improve this script by adding support for more robust and secure email systems, I would be happy if you submitted a PR to do just that :)

            • 8565@lemmy.quad442.com
              link
              fedilink
              English
              arrow-up
              0
              ·
              1 year ago

              Don’t lose your passwords and leave closed registration so only people you actually want on your instance are on it. You absolutely do not need email.

              • netburnr@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 year 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.