Spyke

Replies

Comment on

Want to selfhost a Lemmy server

Reply in thread

it's alright, i run a personal server with closed registrations. looking for new communities is a bit glitchy, you might need to search a few times before it appears.

e: one thing i have to note is that docker-related documentation is somewhat inaccurate and, in my opinion, their setup is a bit overcomplicated.

Comment on

domination is inevitable

Reply in thread

recent events with beehaw have shown that being on a large instance does not guarantee federation.

i'm all for roaming profiles even though i think the best option is hosting a personal or a friends-only instance - unless you're a colossal asshole nobody will defederate you, you're are not depending on anyone but yourself for your profile and subscriptions, etc etc. this obviously isn't for everyone but the barrier of entry is sufficiently low for people interested in tech and fediverse to do just that.

email has started as a fully distributed system but - for reasons too many to count here - ended up centralized over several huge providers, openly dictating rules to everyone else. i'd rather fediverse not followed this road.

Comment on

Want to selfhost a Lemmy server

Reply in thread

  • why use two networks, instead they shouldn't expose any internal ports if using reverse proxy container within compose (I'm using a separate external load balancer/reverse proxy, so I exposed lemmy & lemmy-backend only);
  • stuff like hostname: shouldn't be needed because it matches service name;
  • instead of using generic nginx container image with custom nginx.conf you need to place somewhere manually they should pre-build a container which would work OOTB with the compose setup, this would also solve current situation where nginx.conf and compose file are seemingly maintained separately because they don't match (i had to change one to match the other);
  • a minor thing but i would appreciate environment-based setup instead of needing configuration files (lemmy.hjson) on the filesystem (my ansible-based container deploy system has provisions for this stuff, still its something that i'd rather not have to use...);
  • in general compose setup feels like development environment because of all the debugging that is enabled, i think it also tries to build one of lemmy components instead of using an image by default;

it's all minor stuff, really, but it adds up and people who are not particularly savvy might give up on self-hosting lemmy because of if. so some polish and cleanup might be a good idea.

i know there's an ansible role too but i haven't looked through it. i have to do way too much ansible code review & refactoring at work. :)

Comment on

Docker-compose help (lemmy selfhosted)

every time i see this compose file my head hurts

  • so much debugging enabled
  • two networks for whatever reason
  • bespoke logging setup instead of just using system default
  • host mounted directories instead of docker volumes
  • postgresql exposed for whatever reason

it's a development setup. devs really need to put a production enduser version of this out there.

Comment on

*Permanently Deleted*

Reply in thread

i've lived through the fall of USSR so i consider modern communists incredibly naive but i wouldn't try denying them their freedom to express themselves.

as opposed to people who run around calling everyone they disagree with nazis just so that nobody would dare argue against them.