this post was submitted on 16 Jun 2023
59 points (100.0% liked)

Selfhosted

39939 readers
413 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hey. I really like the idea of the fediverse and Lemmy and would want to know as a beginner/not so experienced regarding selfhosting what would be the best way to get started? I saw there are vps options, but don't know of I'm looking in the right direction.

you are viewing a single comment's thread
view the rest of the comments
[–] blackstrat@lemmy.fwgx.uk 16 points 1 year ago* (last edited 1 year ago) (3 children)

The docker documentation is not kept in sync with the docker-compose.yml it asks you to use. So you download the latest one as per instructions, but that's being regularly updated with no thought to the documentation also being updated. It's also doesn't seem aimed at production deployment, just developer test environments. Then there are stupid simple things like the port number being changed in the docker-compose.yml but not in the nginx.conf or the lemmy.hjson. There desperately needs to be better control of that.

There is a lot wrong there and it doesn't fill me with confidence. It took me 3 hours to piece it all together last night and had to revert to picking bits out of the ansible documentation.

[–] Wander@yiffit.net 6 points 1 year ago

Right? Thank you for confirming that I'm not extremely stupid when I didn't manage to get the docker installation working, only the Ansible one.

[–] kristian@lemmy.astheriver.art 5 points 1 year ago (1 children)

Exactly, I’ve spent ages yesterday and today trying to piece together a set of configs that all work together. I thought it must have been me missing something because the last time I did it everything worked exactly as described in the documentation and it took about ten minutes to get a working instance up and running, but not this time!

It helps slightly (slightly!) if you refer to the configs from the last release rather than the ones on the main branch that are constantly being changed, but even then you’ll have to maybe use the docker-compose.yml from the Ansible repo if you don’t want to build nginx as part of the docker install.

Got there in the end though!

[–] blackstrat@lemmy.fwgx.uk 3 points 1 year ago

Turns out I can't upload photos due to the config file they point you at being wrong. Ffs! Direct users to a labelled release and production version. At the moment it's chaos at the very time it needs to be as seemless as possible.

[–] nocaptchaforme@lemmy.world 2 points 1 year ago

I thought I was going crazy. I'm glad I wasn't the only one having issues.