so it’s an electron web app you could instead of in-browser web ui?

looks very nice, thanks. would appreciate better documenting of SMTP options (login & password) and support for Authelia.

Syncthing has never failed me.

thanks, I guess I missed it. gonna update ASAP just in case, even though I’m the only user of my instance.

unfortunately there’s no images for 0.18.2-anything yet :(

systemd is a godsend when you need service control while getting actual work done, at scale.

there are legitimate things to criticize but in general the rants are incompetent preaching to the uninformed.

very nice, updated with zero issues.

if you pass all outbound connections through vpn you’ll be fine.

i’m hosting lemmy on a vds using an S3 storage hosted at home (over wireguard). :)

i’ve decided against hosting lemmy at home because there’s no way to setup a proxy for outbound connections (or i couldn’t find it) so any federation request your lemmy instance makes reveals your home IP to owners of that particular instance.

re: container logs issue, the proper fix is setting this once in daemon.json (which is what you did) and fixing this issue node-wide instead of adding custom logging into compose files, unless the situation requires it (we had an application which had to use gelf for, oh god) which isn’t the case here. i just have an ansible role to deploy docker which configures logging, among other things.

agree that multiple networks may have a use but definitely not in this particular case.

I always see docker compose files like this as a starting point

same here, unfortunately not everyone has necessary expertise to do that, default setup linked on the project page shouldn’t be this half-baked.

also, unless they fixed it already, 3 days ago compose file and nginx.conf had mismatching ports so it would just never work ootb.

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.

replace the whole build: yaml block with image: dessalines/lemmy:0.17.1

also bump both versions from 0.17.1 to 0.17.4

i suggest pointing pictrs to (an external) S3 backend instead of using a pvc in your README example. minio is much easier to deploy than ceph.

as far as i remember, processes run inside container as root (0:0) end up under your own UID.

everything else gets mapped to those weird UIDs.

S3 support is a good thing, thanks for mentioning it.

• 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. :)

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.

I don’t like nextcloud very much but its calendar impelementation is more than good enough. I could use a separate caldav server but outside of nextcloud I couldn’t find any functional web frontends. Nextcloud has both and it generally just works. Works just fine with android (calendar sync & todo).

NNTP gate would be a cool thing to have, imagine posting via Gnus/Emacs like 20 years ago.

ingress traffic to lemmy is obvious (CF -> reverse proxy, for example) but what about egress traffic i.e. federation requests? I kind of poked around lemmy backend / issue tracker but didn’t find any way to setup a HTTP proxy for backend requests, so your real IP would be visible to any instance you contact, I think.