Deploy Lemmy the easy way! Contribute to ubergeek77/Lemmy-Easy-Deploy development by creating an account on GitHub.
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.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Were you able to get AWS to open port 25 for smtp support?
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.
Yeah, I tried and failed. They denied it and told me to use SES lol.
Whatever haha
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.
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