ubergeek77

Eventually? We already had that two weeks ago!

I plan to support this for as long as I'm using Lemmy, which should be a good while.

All the script really does is generate a docker-compose.yml stack that's best for your desired setup. So even if I do stop supporting the script, you're not locked into using it. You can always manage the Docker Compose stack manually and do your own updates, which is what people not using my script will have to do anyway.

Also, I don't bake Lemmy versions directly into this script, I just pull the latest Lemmy version from GitHub and deploy that. So in theory, unless the Lemmy team changes something major, this should continue working for a long time after I stop supporting it.

If you want to be prepared, I would recommend reading up on Docker Compose and getting familiar with it!

Shameless self plug:

https://github.com/ubergeek77/Lemmy-Easy-Deploy

All you need is a server, a domain, and your DNS records set to your server's IP address. After that, my script takes care of the rest!

Please let me know if you have any issues! I am constantly keeping this updated based on people's feedback!

Running so many Lemmy instances against the same database doesn't cause race conditions? I wonder why that "just worked" so easily, usually load balancing DB-backed apps is a whole beast on its own.

It's 2 hours until July 2nd CST and Boost is still working.

Not only that, I can see NSFW posts. Regardless of if Boost's token didn't get disabled, wasn't Reddit supposed to stop sending NSFW posts through the API?

What is going on?

Try again with the latest version of Lemmy Easy Deploy.

I am now building multiarch images for 0.18.x, and my script will now default to my multiarch images, so there is no longer a need to build it yourself :)

Is this real??? He said he wasn't going to do this 🤔

He said he would not be doing Boost for Lemmy, and that he would focus on smaller apps:

https://www.reddit.com/r/BoostForReddit/comments/14ehiqs/comment/jow1le5

And he only registered the Lemmy community to prevent impersonation:

https://www.reddit.com/r/BoostForReddit/comments/14ehiqs/comment/jouvuok

I wonder if he put this on the store as a placeholder to also prevent impersonation?

EDIT: Damn, just saw the screenshots. Either this is a very elaborate placeholder, or it's really happening!

Thanks!

I've got that included in a staging version I'm preparing to release, if you wanted to take a look at the changes:

https://github.com/ubergeek77/Lemmy-Easy-Deploy/issues/17

I see. Thanks a lot for this!

I really don't have the capacity to support a bunch of different email services, so it sounds like the best I can do right now is make the SMTP settings accessible without also running the postfix server. So if someone wants to run their own email somewhere else, they can configure it. But otherwise, I'll leave it to the user to figure out what happens after an email request leaves Lemmy.

Does that sound fair, and like something you would have used? Essentially just an interface in config.env that puts the right SMTP address/credentials in lemmy.hjson.

Before this week, I would have told you no. But I have big plans for the 0.18.1 update.

The Lemmy team has completely broken ARM support with seemingly no plan to support it again. They switched to a base Docker image that only supports x86_64. This is why your build fails. I still don't understand why they would move from a multiarch image to an x86_64-only one.

I've been working on this for about a week, and just yesterday I finished a GitHub Actions pipeline that builds multiarch images for x64/arm/arm64. I currently have successful builds for 0.18.1-rc.2. In a future update for my script, I will have it use these, that way ARM users don't need to compile it anymore. I just ask for a little patience, I haven't been able to do any work on Lemmy Easy Deploy since I've been working on this pipeline :)

I also do want to qualify - don't get your hopes up until you see it running for yourself. Ultimately, I am just a DevOps guy, not a Lemmy maintainer. I haven't tested my ARM images yet, and while I did my best to get these to build properly, I can't fix everything. If anything else breaks due to running on ARM, it will be up to the Lemmy team to fix those issues (which is not likely anytime soon, if their updated x86_64 Dockerfiles are any indication).

But, fingers crossed everything goes smoothly! Keep an eye out for an update, I'm working hard on it, hopefully I can get it out in time for 0.18.1!

EDIT:

Of course I had to just go and open my mouth. This doesn't look good. I may need to remove ARM support from Lemmy Easy Deploy entirely until Lemmy figures this out :/

I haven't actually used the embedded postfix server at all, I keep mine disabled. I only include it because it's "included" in the official Docker deployment files, and I try to keep this deployment as close to that as possible.

I'm considering adding support for an external email service, as you mentioned, but I have nearly zero experience in using managed email services, and I'm not sure if non-technical users would be able to navigate the configuration of things I can't do for them (i.e. on a web dashboard somewhere). And if I can't do it for them, it means more issues for me, so I hesitate to add support for it at all.

I'd love to hear your experience in setting up sendgrid and how easy that was. And the tracking stuff you mentioned as well.

Yep. It's all manual. There are hundreds of Lemmy instances out there, new instances have no way of discovering any of them unless you tell it how.

Federation with a community only has to happen once. After it's connected, the instance will always receive new data and posts from that point forward. That is why the major public instances always have posts from a wide variety of instances.

But, only a single person needs to do the federation, it doesn't have to be done by an admin. After the connection is made with a community, content from that community will start showing up on "All" for that instance for everyone.