Selfhosted

39257 readers

183 users here now

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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

208

Having trouble deploying Lemmy? Try my new script! Get up and running in minutes! (github.com)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

131 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

I think I have successfully got the server running on my linode.

[–] [email protected] 1 points 1 year ago (1 children)

I'm glad to hear that! Thanks for letting me know, it's nice to hear people were able to use my script to get up and running :)

[–] [email protected] 0 points 1 year ago (1 children)

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.

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (1 children)

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

Give it a few seconds, until you either see "No results" disappear, or until you see it show up as " - 0 subscribers" in the search results. This works for kbin communities too!

You might see some people say to search it like [[email protected]](/c/[email protected]), but I have way more success with doing it with the actual links. 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!

[–] [email protected] 0 points 1 year ago (1 children)

Wait, so pardon my noobism, but does this mean you need to federate with communities manually? Don't instances start out as already being federated with everything?

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago

Oh, okay, fair. So this means that the search for new communities to browse/federate with is less troublesome, the more users populate an instance. On the flip side, if I'm considering self-hosting as one single user, I should anticipate:

having a fairly long phase of community discovery, unless I already know which communities I'm interested in;
that those communities that I do federate with will not give me any data prior to the moment I federated with them (is there a cache system to avoid this? can I go specifically retrieve older posts?)
an important need for storage space, as I essentially become a duplicate of the server for every community I federated with, from that point on.

Is this correct?