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
    1·
    1 year ago

    To be honest, I have no idea how the public instances have favicons right now. I can tell from my own instance’s HTML that Lemmy isn’t sending any favicon data.

    What confuses me is, the place where lemmy.world and lemmy.ml have it rendered is here, via Helmet, but setting your own icon is not documented anywhere, and I don’t see anything in Helmet’s code that grabs a favicon URL.

    It looks like 0.18.0 will more explicitly set the favicon URL, but it doesn’t look very configurable to the end user. Looks like it’s hardcoded to a string in the build props, or to a default string pointing to the default svg. So it might be that all the public instances are just recompiling the entirety of lemmy-ui just to set a custom favicon.

    Once 0.18.0 comes out, I will see how favicons are handled by default, and maybe provide a volume interface for replacing that default image.