▪█─────█▪
just raise awareness about tools like this one https://lemmyverse.net/
I also think that something like LCS or Lemmony should be recommended and/or included in the default Lemmy docker compose file.
That way, when new Lemmy servers get spun up, they will automatically get seeded with content and communities from other existing Lemmy servers.
At work/for business, you can’t beat Veeam. It’s the gold standard and there is literally nothing better.
At home, Duplicity. Set it up once and then just let it go, and it supports a million different backup targets you can ship your backups off to, including the local filesystem. Has auto-aging/removal rules, easy restores, incrementals, etc. Encrypts by default too.
I think that this line of reasoning becomes less and less tenable when things like Swagger exist.
I just wished the Lemmy API docs were better lol.
Finnegans Wake makes more sense than Lemmy API docs. Even calling it “documentation” is a stretch.
I literally had to clone the Lemmy git repo and read the source code to find the implementation of an API endpoint and see how it worked for a script that I was writing.
It’s a decade later, and I’m still bitter about Google Reader’s unceremonious execution.
“No, I can’t come out tonight, I’m optimizing my CONFIG.SYS file so I can have a mouse AND my Soundblaster work at the same time!”
Man I loved Encarta. I would spend hours in that shit just going through random stuff.
Then there’s the hostility if a post does get play.
I used to dread seeing that new message notification icon.
And here you are with 53 comments in 6 days.
docker (while you don’t need it to host things, it makes your life 10x easier)
…until you have a single extra space character hiding 20 lines into your compose file and the whole thing falls over the next time you try to bring the containers up.
Lint your code and configs every time!
Make sure the postfix container is connected to the lemmyexternalproxy network.
Make sure the networks section at the top of your docker compose file looks like this:
I’m seriously missing the ability to jump to the current/next/previous parent comment. I make heavy use of that and only Jerboa has it right now, I think.
You’re welcome! Docker/Docker Compose are a great tools once your wrap your brain around them and why containers are ephemeral, etc. Docker’s docs could really use improvement though, you never know if what you’re looking for is in the section that’s dedicated to to that feature, or if the only mention of it is buried deep in the 10th sentence of the 20th paragraph on a completely different page that has absolutely nothing to do with what you’re looking for.
Docker at this depth is a bit new to me. Curious. Why does it need to be bound to the lemmyinternal and lemmyexternalproxy nets, and not just internal?
Because the “lemmyinternal” network is set as an internal type network in the Docker compose file, which is exactly what it sounds like: internal-only. Postfix wouldn’t have a way to egress to the WAN if not connected to the “lemmyexternal” network, so the initial connection step to send the mail from the “lemmy” container would work, but postfix sending it would fail, as it doesn’t have a route out to the Internet.
It’s because the postfix docker container is not connected to a docker network that has access to the “lemmy” or “lemmy-ui” container, it’s being connected to the “default” docker network. I submitted a pull request for it here that should fix it.
To make it work in the meantime:
cd into the Lemmy install directory and run docker compose down
Edit docker-compose.yml in the same directory, and in the postfix section, put this just below the postfix: line:
networks:
- lemmyinternal
- lemmyexternalproxy
Run docker compose up -d
The indentation of that code is very important. Your postfix section should look like this when it’s done:
That should connect the “postfix” container in to a docker network that can communicate with the “lemmy” and “lemmy” UI containers. There’s another bug in the default config that doesn’t assign a hostname to all the containers, but it doesn’t always manifest all the time. You can fix that by making sure each service has a hostname assigned to it, like hostname: lemmy, hostname: lemmy-ui, hostname: postfix etc in the respective service’s section of the service: section of the docker compose file.
How are they going to determine which apps have free API access without this definition!?
If there’s one thing that I’ve learned from this trainwreck, it’s that they’re not going to define it publicly. If the internal definition is fluid, it can serve as a moving target to be whatever is most beneficial to them at the time.
I’ve been a RiF diehard for about a decade, but I’ll definitely give Sync for Lemmy a try when it’s available.
What I’m really interested in is this. If this gets completed, theoretically any existing third-party reddit app could update the API URL it hits and their app would pretty much “just work” with Lemmy, they’d just need to add an option for the user to input their home instance’s URL and their credentials. It was started by @derivator
I desperately want a RiF clone for interacting with Lemmy. If RiF does actually shut down at the end of the month, I really hope talklittle open-sources it.
So I’m not the only one who fried a monitor trying to get X11 working…