128
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Jun 2023
128 points (97.8% liked)
Selfhosted
39239 readers
270 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:
- 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
Have you tried searching for the communities first? As I understand it from some other posts, if you try to access a remote community via URL through your home instance before it "knows" about it, you'll get the 404 error. Someone (you) on your instance has to make your instance "aware" of the remote community by searching for it first. Then, after your instance is aware of the community and federating it, you can access it via URL as you posted above.
THANK YOU
I didn't remember doing this for the first two, but I guess I must have. (I would reply from there, but comments haven't synced yet, which I guess is expected)
I'm glad that worked. I'm considering launching a personal self-hosted instance of my own, so I may be in your shoes soon enough.
How did you find the process? Did you use Docker or Ansible?
If you can read this, the Ansible playbook mostly Just Worked™ to install it on a clean Debian VPS. I actually did start over at one point because I wanted to change the domain name after learning there's not currently any way to use different domains for the UI and usernames like there is in Mastodon (relevant github issue); from that, I suspect it should be good about not clobbering anything except maybe SSL certs for existing nginx sites.
For some reason, my nginx also now seems to try to use the cert lemmy installed by default, even on a site I just set up to only listen on port 80 (http://gillen.dev). So that's kinda weird, but just installing a new cert for such a site with certbot fixes it (https://sdg.fyi).
It still seems to be struggling a little bit: votes and comments on this thread are taking a looong time to show up here (your comment just got here and it says it was from 24 minutes ago)... or maybe I'm just impatient :)
Of course, the real test will be when it comes time to update to the next Lemmy version...
Thanks, that's good info. If I do go forward, I was planning on going the Ansible route, though I've never used it before.
I've read that it can take a bit of time to sync when you first federate, but that after some period of time it gets closer to real-time with posts and comments.
it is easy enough. Simply run the playbook again. well, git pull the ansible playbook again and then run it. alternatively you can just use docker compose now on your lemmy server. I made some aliases on my lemmy instance based on what i use elsewhere. I think I got them from a linuxserver.io tutorial ages ago. you will need to adjust the container versions for this to be viable as the version is hardcoded and they only have a "latest" tag for arm.