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

    • ubergeek77@lemmy.ubergeek77.chatOPEnglish
      0·
      2 years ago

      Sorry, I don’t have access to an unRaid system to test it with.

      However, I know most NAS systems at least support CLI-style Docker and Docker Compose, so if you can manage to get Docker running, it might work? The script has some Docker detection if you’re not sure.

      However, I know Synology hogs use of port 80 and 443. I’m not sure if unRaid is the same way. If it is, this might not be the best solution for you. But, if you want to give it a shot, I do have some advanced options in my config that lets you change to different ports and turn off HTTPS (so you can run a proxy in front of it). I can’t really help people who run it behind a webserver like this, but the template files in my repo can be freely modified, so you’re welcome to hack at my script any way you like to get it working!

  • untilyouarrived@lemmy.gtfo.socialEnglish
    0·
    2 years ago

    I’m relatively competent installing server software, but the Lemmy instructions completely flummoxed me. Their docker instructions just don’t work.

    I ended up using the ansible docker scripts and filling out the blanks because I’m unfamiliar with ansible.

    If this is as good as it sounds, you’re doing everyone a massive favour.

  • kuna@szmer.infoEnglish
    0·
    2 years ago

    Do I understand it correctly that this script only works if it can set up it’s own Caddy, and if I already run nginx to reverse proxy stuff on my server, then this isn’t for me?

  • marketingpro123@kbin.social
    11·
    2 years ago

    Exploring Go High Level:

    What’s the Enthusiasm About?
    Hello there! Are you familiar with Go High Level? If not, let’s break it down. Imagine managing multiple apps for marketing. Sounds busy. That’s where Go High Level comes in. It’s like that friend who has a solution for everything. Whether you are working on creating an outstanding sales funnel or sending out an email campaign, this platform has your back. The best part? They let you test drive everything with a 14-day free trial. It’s like trying out a new car but for your business. And if you ever need assistance, their support team is just a click away. Pretty exciting, huh?

    So, How Much Does It Cost?
    Alright, let’s talk about the financial side. Go High Level offers 3 main plans. The Agency Starter Plan is perfect if you’re just starting or have a small business. It’s loaded with all the essential tools, and it’s quite cost-effective. But if you’re looking to scale up, the Agency Unlimited Plan is your best choice. It’s like the VIP pass at a concert, giving you access to everything without any limitations. Not sure about committing? Remember that 14-day free trial I mentioned? It’s a great way to give it a try without any obligations. Lastly, they offer a Pro plan that includes “SaaS mode,” where you can white label the product under your brand. Fantastic!

    Why Everyone’s Raving About It:
    In a world full of sophisticated digital tools, Go High Level is like that all-in-one Swiss Army knife. There’s no need to switch between apps because it has everything under one roof. Whether you’re a newcomer or an experienced marketer, it’s super user-friendly. It’s not just about launching impressive campaigns; they ensure you understand their performance with top-notch analytics. There’s even a white-label feature for marketing agencies, so you can add your brand and impress your clients.

    Here is a link to their 14-day free trial:
    https://www.gohighlevel.com/?fp_ref=get-started-now.

    • ubergeek77@lemmy.ubergeek77.chatOPEnglish
      0·
      2 years ago

      I haven’t tested a local only use case, but you can probably set these options in config.env

      • Set LEMMY_HOSTNAME to localhost
      • Set CADDY_DISABLE_TLS to true
      • Set TLS_ENABLED to false

      This will disable any HTTPS certificate generation and only run Lemmy on port 80. I don’t know if Caddy or Lemmy will act weird if the hostname is localhost, but this should work for you. Let me know if it doesn’t.

      • ChaosAD@lemmy.worldEnglish
        0·
        2 years ago

        Sorry to bring more problems to you.

        SOLVED: The problem was caused because I was using a | In the site name SETUP_SITE_NAME

        for some reason the bash script is returning sed: -e expression #7, char 32: unknown option to `s' I 've looked online and found nothing that related to my problem. I suspect the problem starts in line 253 because the file lemmy.hjson is empty and the docker-compose.yml isn’t created.

        • ubergeek77@lemmy.ubergeek77.chatOPEnglish
          0·
          2 years ago

          Good catch!

          I will make a note in the example file about this. You can use special characters if you want, but you’ll need to backslash escape them first. So in config.env, you probably could have done:

          SETUP_SITE_NAME="Lemmy \| Server"
          • ChaosAD@lemmy.worldEnglish
            0·
            2 years ago

            hi! do you have some IM we could talk please? I am getting insane haha, trying to bring up a server for 4 days now lol I think your method is the closest to work but I am getting something wrong.

              • ChaosAD@lemmy.worldEnglish
                0·
                2 years ago

                OK! So here we go.

                I already use Caddy on my server because of other services I have running so I was afraid it could conflict with the caddy container in the docker-compose you provide, so I disabled caddy service just for testing and afterwards I could try to figure how to make it work alongside my current configuration. But for some reason I can’t get my domain to connect to the instance.

                So I decided to try different and do not install the caddy container and use the one I have running natively. So I just coppied the Caddyfile content that is generated by the deploy.sh and replaced the env variable with my domain name (just to make sure it would work).

                I changed the docker-compose.yml to this:

                version: "3.9"
x-logging:
  &default-logging
  options:
    max-size: '500m'
  driver: json-file

services:

  lemmy:
    image: dessalines/lemmy:0.17.4
    environment:
      - RUST_LOG="warn,lemmy_server=info,lemmy_api=info,lemmy_api_common=info,lemmy_api_crud=info,lemmy_apub=info,lemmy_db_schema=info,lemmy_db_views=info,lemmy_db_views_actor=info,lemmy_db_views_moderator=info,lemmy_routes=info,lemmy_utils=info,lemmy_websocket=info"
    volumes:
      - ./lemmy.hjson:/config/config.hjson
    depends_on:
      - postgres
      - pictrs
    networks:
      - lemmyinternal
      - lemmybridge
    ports:
      - 8536:8536
    restart: always
    logging: *default-logging

  lemmy-ui:
    image: dessalines/lemmy-ui:0.17.4
    environment:
      - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536
      - LEMMY_UI_LEMMY_EXTERNAL_HOST=localhost:1236
      - LEMMY_HTTPS=true
    depends_on:
      - lemmy
    networks:
      - lemmyinternal
    ports:
    #Always keep em guessing
      - 1236:1234
    restart: always
    logging: *default-logging

  pictrs:
    image: asonix/pictrs:0.3.1
    user: 991:991
    env_file:
      - ./pictrs.env
    volumes:
      - pictrs_data:/mnt
    networks:
      - lemmyinternal
      - lemmybridge
    restart: always
    logging: *default-logging

  postgres:
    image: postgres:15-alpine
    environment:
      - POSTGRES_USER=lemmy
      - POSTGRES_DB=lemmy
    env_file:
      - ./postgres.env
    volumes:
      - postgres_data:/var/lib/postgresql/data
    networks:
      - lemmyinternal
    ports:
      - 5432:5432
    restart: always
    logging: *default-logging

networks:
  lemmyexternalproxy:
  lemmybridge:
  lemmyinternal:
    driver: bridge
    internal: true

                Placed all the .env in the same folder of the docker-compose.yml and placed the lemmy.hjson in this same folder too.

                {
  setup: {
    admin_username: "lemmy"
    admin_password: "sjhdakjhsdjhasdkjashdjkahs"
    site_name: "Lemmy"
  }

  hostname: "lemmy.domain"
  bind: "0.0.0.0"
  port: 8536
  tls_enabled: true

  pictrs: {
    url: "http://pictrs:8080/"
    api_key: "dkslahlsdjhasjdçlajsçdaskj"
  }

  database: {
    user: "lemmy"
    password: "jahdskjhadjsappdsiadopisap"
    host: "postgres"
    port: 5432
    database: "lemmy"
    pool_size: 5
  }

}

                runned the docker-compose up -d and everything went OK, no errors in the terminal. but still my domain don’t connect.

                I have disabled cloudflare proxy and cache but nothing helped :(

                • ubergeek77@lemmy.ubergeek77.chatOPEnglish
                  0·
                  2 years ago

                  Sorry, combining this with an already-running webserver is not a use case I support for this easy deployment script. My script is intended for new deployments for people not already running servers.

                  The best thing you can do is change the ports in docker-compose.yml.template, and today I will make an update that gives you environment variables for them.

                  Unfortunately I do not have time to help you dig deeper into the issue, but hopefully these tips help you:

                  • Change the ports in docker-compose.yml.template to something that won’t conflict with your webserver. Take note of what port you used for 80
                  • Edit config.env and set CADDY_DISABLE_TLS to true
                  • Edit your own webserver config to point to this deployment via a reverse proxy. I’ll leave it up to you to configure that. You are already using Caddy, so you can look at my Caddyfile for inspiration on how reverse proxies work.

                  Since you’re using your own webserver, doing it this way will not automatically retrieve certificates for you. Hopefully you have a system in place for that already.

                  Good luck!

  • manager123321@kbin.social
    11·
    2 years ago

    Exploring Go High Level:

    1. What’s the Enthusiasm About?
      Hello there! Are you familiar with Go High Level? If not, let’s break it down. Imagine managing multiple apps for marketing. Sounds busy. That’s where Go High Level comes in. It’s like that friend who has a solution for everything. Whether you are working on creating an outstanding sales funnel or sending out an email campaign, this platform has your back. The best part? They let you test drive everything with a 14-day free trial. It’s like trying out a new car but for your business. And if you ever need assistance, their support team is just a click away. Pretty exciting, huh?

    2. So, How Much Does It Cost?
      Alright, let’s talk about the financial side. Go High Level offers 3 main plans. The Agency Starter Plan is perfect if you’re just starting or have a small business. It’s loaded with all the essential tools, and it’s quite cost-effective. But if you’re looking to scale up, the Agency Unlimited Plan is your best choice. It’s like the VIP pass at a concert, giving you access to everything without any limitations. Not sure about committing? Remember that 14-day free trial I mentioned? It’s a great way to give it a try without any obligations. Lastly, they offer a Pro plan that includes “SaaS mode,” where you can white label the product under your brand. Fantastic!

    3. Why Everyone’s Raving About It:
      In a world full of sophisticated digital tools, Go High Level is like that all-in-one Swiss Army knife. There’s no need to switch between apps because it has everything under one roof. Whether you’re a newcomer or an experienced marketer, it’s super user-friendly. It’s not just about launching impressive campaigns; they ensure you understand their performance with top-notch analytics. There’s even a white-label feature for marketing agencies, so you can add your brand and impress your clients.

    Here is a link to their 14-day free trial:
    https://www.gohighlevel.com/?fp_ref=get-started-now.

  • neetly@lemmy.worldEnglish
    0·
    2 years ago

    As someone who spent hours figuring out how to deploy through Ansible, how dare you /s But seriously thank you for putting in the work to make creating an instance more attainable for people.

  • Marxine@lemmy.worldEnglish
    0·
    2 years ago

    You kind Sir/Lady/Gentleperson are making the fediverse a better place with this help. Thanks a bunch, gonna definitely ease my attempts at eventually self-hosting!

  • neetly@lemmy.worldEnglish
    0·
    2 years ago

    As someone who spent hours figuring out how to deploy through Ansible, how dare you /s But seriously thank you for putting in the work to make creating an instance more attainable for people.

      • neetly@lemmy.worldEnglish
        0·
        2 years ago

        I’m just a novice hobbyist (the only server I’ve put together was a homebridge server years ago) so the learning curve for this was relatively high putting together a VPS, setting up ssh, learning how to properly configure, and there were some errors when running the playbook I had to slowly figure out. Honestly though once it was all done, I thought “man, that was actually pretty easy” and I learned a lot so that was really cool

  • Thief@lemmy.myserv.oneEnglish
    0·
    2 years ago

    I used this and the developer is very helpful. Works great. Helped me even upgrade to 0.18.0.

  • ipkpjersi@lemmy.oneEnglish
    0·
    2 years ago

    Wow, I’ll definitely look into this, thanks! Even if I don’t use it, it still may be useful just reading through it.

  • redcalcium@c.calciumlabs.comEnglish
    0·
    2 years ago

    Nice! Looks like it even has update checker as well. Is there any reason why pictrs is not included in the update checker and hardcoded to version 0.3.1?

    • ubergeek77@lemmy.ubergeek77.chatOPEnglish
      0·
      2 years ago

      The Lemmy maintainers themselves seem to lock it at 0.3.1, and I wanted to maintain parity with their deployment. I know pictrs is up to at least 0.3.3, and has a release candidate for 0.4, but upstream Lemmy uses 0.3.1 for whatever reason, so that’s why I lock it there.

      It’s excluded from the update checker because I don’t have a stable way to check what version upstream is using. The Lemmy update checker just checks to see what the latest tag on LemmyNet/lemmy is. I could try and pull the latest Gitea tag for pictrs, but since upstream Lemmy isn’t using the latest version, that’s not really an option as something might break.

      I considered trying to parse their docker-compose.yml file to see what version they use, but they seem to be restructuring their docker folder right now. The folder in main is completely different from the one tagged 0.17.4. If I assume a certain directory path for that file for every version after this, but they move it, my script will break. Sadly, until their Docker deployment files seem like they’re going unchanged for a good few versions, I’ll have to do it manually for now.

      • redcalcium@c.calciumlabs.comEnglish
        0·
        2 years ago

        I see, looks like it’s a correct decision to me. Let the Lemmy developers worry about which version of pictrs to use themselves.

  • falcon15500@lemmy.nine-hells.netEnglish
    0·
    2 years ago

    Looks really good. I did it pretty much the same way, myself - but if I were looking to start again, I would definitely use this.

    Edit: Ran it on a fresh AWS Ubuntu instance and it worked perfectly fine.

      • falcon15500@lemmy.nine-hells.netEnglish
        0·
        2 years ago

        I didn’t bother, as I was just testing. But you are right, port 25 outbound is blocked by default. They have a defined process for you to ask for it to be unblocked and you have to tell them what you are using it for and how you are preventing spam from being sent. In this case it might be enough to say that you aren’t allowing port 25 inbound, so it can’t be used as an open relay.

        • Zach @bigfoot.ninjaEnglish
          0·
          2 years ago

          Yeah, I tried and failed. They denied it and told me to use SES lol.

          Whatever haha

          • falcon15500@lemmy.nine-hells.netEnglish
            0·
            2 years ago

            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.ninjaEnglish
              0·
              2 years ago

              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