Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

214
active users

veganism.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-alpha.4

#Issues

6 posts6 participants0 posts today
Public
N-gated Hacker News

☠️ Oh joy, yet another tale of how #SQLite3 becomes a sardine can when you try to cram in #multitenancy with Rails! 🐟 Apparently, the author's groundbreaking revelation is that ignoring #multithreading makes your app collapse faster than my interest in reading this. 🚀
blog.julik.nl/2025/04/a-can-of #Rails #Issues #SardineCan #HackerNews #ngated

Julik Tarkhanov · A Can of Shardines: SQLite Multitenancy With RailsThere is a pattern I am very fond of - “one database per tenant” in web applications with multiple, isolated users. Recently, I needed to fix an application I had for a long time where this database-per-tenant multitenancy utterly broke down, because I was doing connection management wrong. Which begat the question: how do you even approach doing it right? And it turns out I was not alone in this. The most popular gem for multitenancy - Apartment - which I have even used in my failed startup back in the day - has the issue too. The culprit of does not handle multithreading very well is actually deeper. Way deeper. Doing runtime-defined multiple databases with Rails has only recently become less haphazard, and there are no tools either via gems or built-in that facilitate these flows. It has also accrued a ton of complexity, and also changes with every major Rails revision. TL;DR If you need to do database-per-tenant multitenancy with Rails or ActiveRecord right now - grab the middleware from this gist and move on. If you are curious about the genesis of this solution, strap in - we are going on a tour of a sizeable problem, and of an API of stature - the ActiveRecord connection management. Read on and join me on the ride! Many thanks to Kir Shatrov and Stephen Margheim for their help in this.
Replied in thread
Public
☮ ♥ ♬ 🧑‍💻

Day 26 cont 🍗🥓🍖🍑🥑🍌🥗🥩🥦🥕🍏🍅🥬

“Around 50,000 people turned away from #FoodBanks each month, as charities struggle to keep up with demand, a new report from #OzHarvest has found.

The survey of frontline #charities reveals 77% have witnessed a surge in people seeking #food in the past year, with an estimated 50,000 people unable to be supported every month by responding charities as services simply cannot keep up.”

#AusPol / #politics / #Election / #issues <theguardian.com/australia-news>

the Guardian · Australia election 2025 live: AEC expects half of votes to be cast before 3 May amid pre-polling surgeFollow live
Public
Taha Ahmed

Does anyone know of any project that lets you mirror your issues from code forges (such as Github, Codeberg, etc.) to a self-hosted list of some sort?

I can do something rudimentary with RSS feeds (both Github and Codeberg lets you subscribe to all user actions) and grepping for "issue", but what I would like to see is something that would also mirror associated tags and closed/open status, ...

Just putting the idea out there.

#issues #codeberg #github #selfhosting

links.solarchemist.se/shaare/r

links.solarchemist.se · Idea: mirroring all your issues from code forges to a self-hosted listSomething I would like to be able to do: mirror all my issues that I own from across various code forges (Github, Codeberg, etc.) into a single list of my choosing, for example, as an RSS feed or a Markdown list or whatever. Actually, as RSS feeds this already works (one feed per forge). But what I
VegansExploreLive feeds
About