Distrobox ftw
falcon15500
joined 2 years ago
Depending upon how many users you are looking to host, Lemmy instances are not very taxing. Most instances are on quite modest hardware.
Because of this thread, I signed up to healthchecks.io and configured it with gotify - similar to ntfy, I guess. Have a cron job checking my Lemmy instance is returning 200 every 15 minutes and then pinging healthchecks.
Try searching either way and wait. At first it will show "No results" or similar but after about 10 seconds it should go away. Then either the result will show, or you need to change selector to "Local" (its a bug). But you need to wait for "No results" to go away.
Stoked to have found this community, as I'm very interested to start brewing after I move to my new house.
Have never brewed previously but have have sampled my fair share!
Will be keeping an eye out for pearls of wisdom and will likely ask a question or two.
You need to make sure you are pulling the images for your arch - the default ones are for x86_64. Check the docker hub pages for each, specifically the "Tags" tab.
Sorry... I am not understanding fully, I think. So you want to see if posts on your self-hosted instance will propagate to other instances? In this case, only if someone on the other instance has searched for your community.
It's not distributed architecture as you normally think it - it's a decentralised federation. It's an important distinction from your typical distributed architecture app.
None of them are much use on the Lemmy container because it only exposes the ports required for it to work and it doesn't have SSH. You would normally have SSH keys only and a firewall on the docker host. You could likely use something like crowdsec on the reverse-proxy logs to catch stuff.
A +1 from me for Caddy. It works quite well.