Selfhosted

39948 readers

315 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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Help standing up a self-hosted Lemmy instance (lemmy.world)

submitted 1 year ago by [email protected] to c/[email protected]

21 comments fedilink hide all child comments

I'm trying to stand up a Lemmy instance, and for some reason I'm just not getting it. I've got a fair bit of experience in Linux and Docker. NPM is new to me, but doesn't seem difficult.

I've looked over several walkthroughs but it seems like they all don't quite work right. Does someone have a clear step-by-step that works, or could take the time to remote in and help me get this up?

I'm running on VMWare ESXi, and I've tried both Debian and Ubuntu to get the server up. Closest I got, the Docker containers would start but seem to be throwing errors internally and don't connect to one another.

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

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

I just set it up from a git checkout, and it was pretty involved -- the build instructions are actually quite a bit better than usual for development software at this stage, but it's still a complicated process with some changes vs. what's in the instructions. If you're open to that route, I can try to document what I did in more detail + send it along and give some help if you get stuck.

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

Not the OP but I would appreciate it. I got stuck with building the lemmy image. Not sure why they don't just use a published image

EDIT - found the problem - the docker compose file has the build options enabled for the lemmy image and the published image commented out

EDIT 2 - latest issue - 404: FetchError: request to http://lemmy:8536/api/v3/site? failed, reason: getaddrinfo EAI_AGAIN lemmy

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

I had an AI write 95% of my kurbenetes config. I had this at one point, it is likely you are not proxying (usually nginx) the Lemmy backend to /api and there are are other endpoints that need mapped to it too.

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

The furthest I got last night, that was where I got stuck as well.