Couple of days ago ‘honey I shrunk the vids’ was posted here, a very lightweight tdarr alternative. https://piefed.ca/c/selfhosted/p/571213/honey-i-shrunk-the-vids-mr-universe-edition-v1-0-5
But I haven’t tried it - I’m not sure if it’s perhaps gui-only, and it seems to be AI coded to a certain degree, so YMMV.
Conversations is working very well on my phone as UP distributor.
On a more personal note, still eagerly reading your updates here every couple of weeks. Sounds like it’s shaping up nicely!
Good luck with the api wiring to let people control the forges directly from the interface for 1.0 - if you ever need a tester for forgejo integration you can hit me up.
While the comment was obviously a bit rude, perhaps you can take something constructive out of it. I see that you have a nice compose file prepared as an example with postgres, and a curl into bash for ‘automatic installation’.
Many feel a bit uncomfortable with doing that - especially if the script ultimately just sets up docker containers again. Maybe you could add a ‘quickstart’ section there which just consists of a single docker run command setting up the sqlite version.
That way you have the best of both worlds and both people wanting a production setup example and those just wanting to quickly try are served.
I have long had a switch to pangolin for my homelab services on the roadmap. Can you explain what you mean with internal connections making more sense?
That’s really cool. After I replied I also remembered you can have multiple libraries in audiobookshelf so even if side-by-side doesn’t work it shouldn’t be an issue.
Unfortunately I love my Readest reading app too much to switch away but it’s nevertheless good to know for other family members.
Wait you use it also for epub/pdf? How does that work, can you connect a client and grab it from there? Can you have both an audiobook and text version of the same book?
Just in case you wanna try again with readarr, after all the little drama and the main app being unmaintained, there’s 2 forks which are maintained and work pretty well
I’ve successfully been running bookshelf for a bit now, after the original stopped working for me completely.
The code forge is gitea/forgejo, and the proxy in front used to be traefik. I tried fail2ban in front for a while as well but the issue was that everything appeared to come from different IPs.
The bots were also hitting my other public services pretty hard but nowhere near as bad. I think it’s a combination of 2 things:
A small interesting observation I made was that they also seemed to ‘focus’ on specific projects. So my guess would be you get unlucky once by having a large-ish repo targeted for crawling and then they just get stuck in there and get lost in the maze of possible pages. On the other hand it may make targeted blocking for certain routes more feasible…
I think there’s a lot to be gained here by everybody pooling their knowledge, but on the other hand it’s also an annoying topic and most selfhosting (including mine) is afaik done as a hobby, so most peeps will slap an Anubis-like PoW in front and call it a day.
I’m providing hosting for a few FOSS services, relatively small scale, for around 7 years now and always thought the same for most of that time. People were complaining about their servers being hit but my traffic was alright and the server seemed bulky enough to have a lot of buffer.
Then, like a month or two ago, the fire nation attacked the bots came crawling. I had sudden traffic spikes of up to 1000x, memory was hogged and the CPU could barely keep up. The worst was the git forge, public repos with bots just continuously hammering away at diffs between random commits, repeatedly building out history graphs for different branches and so on - all fairly intense operations.
After the server went to its knees multiple times over a couple days I had to block public access. Only with proof of work in front could I finally open it again without destroying service uptime. And even weeks later, they were still trying to get at different project diffs whose links they collected earlier, it was honestly crazy.
I ended up adding go-away in front of my code forge and anything showing dynamic info, and it turned out to be way less of a hassle than I feared with two redirects and a couple custom rules.
If you already have traefik redirecting to your services, shouldn’t be too tough to get the extra layer of indirection added (even more so if it’s containerized).
Wow, this looks like it has the potential to become something very very special. I already love the various forge integration possibilities and with a couple more upcoming block types (already dreaming of Nextcloud integration or perhaps even custom blocks) this could be an amazing planning hub.
Well done, I’ll definitely keep an eye on this!
A fantastic resource, thanks for posting this!
It’s an interesting concept that I also started exploring last year, though somewhat less extreme.
My deployments run on incus containers/VMs which are spun up by terraform. Those may in turn host things e.g. through docker or just bare-metal.
But instead of going full packer-golden image, my principle orchestration is still done by Ansible which prepares the bare-metal host, gets incus rolling, and then starts the terraform process, before taking control again and operating on the now spun-up individual machines.
Lidarr is configured with folder C, which is a mergerfs volume consisting of folder A and B. Folder A is read-only, and any writes on C go into folder B. This way Lidarr can “see” all my existing music, while any automated downloads go into folder B, keeping them separate from my organized files.
That is so dang clever I definitely have to steal the idea.
Nametag […] launched this past week and filled the void left in many of our lives by Monica
I think I’ve been out of the loop here, what happened to Monica?
No I think the OP is confused. tt-rss forums was a largely horrible community which prided itself on being edgy and toxic. FreshRSS never had anything to do with them, except for also being an rss reader. It is (or at least was? Not sure nowadays) instead loosely connected to the framasoft people, who are cool and doing nice things for the open source community, and not at all toxic.
Fascinating read, I should definitely also make way more use of sqlite for little side projects.
Thanks for the link!
While a full ‘deletion’ of such an issue is certainly unfortunate, I can kind of see how it gets to such a decision point.
You’re creating some software in the open, decide to ping some communities on reddit/lemmy and all of a sudden it seems like a disgruntled brigade is breaking down your door while you just wanted to show them the garden.
What for us looks like earnest sleuthing can feel like abuse/harassment from the other side simply due to the asymmetrical nature of the internet.
Would have probably still preferred a closed issue instead, but having a couple ‘niche-successful’ repos on github myself - I can at least certainly empathise.
While I’m a big proponent of version pinning your critical services, if you’re running stuff in docker swarm shepherd is a solid service updater for the less critical things.