u/ollieread

I've been doing Laravel multitenancy for years and kept seeing teams reach straight for a database per tenant, mostly because it's hat most of the popular packages offer by default. So I wrote up the whole spectrum of data isolation approaches. Separate instance, separate database, schemas/prefixes, partitioning, and discriminator column, along with how each behaves across PostgreSQL, MySQL/MariaDB and SQLite, and where row-level security changes the picture.

The short version: for most apps a discriminator column with RLS on PostgreSQL gets you real, database-enforced isolation at the lowest operational cost, and database-per-tenant is the most expensive answer to a question most apps can answer cheaply.

As with everything when it comes to development, the answer is often "it depends", so I'd love to hear from anyone about their experiences with this, whether good or bad.

I started collecting Tau when they were first released, and they were always my army of choice. It has been many years (read: 20) since I've touched Warhammer, and I've recently realised that as an adult, I have adult money and can just buy things.

So, I've got myself a nice big stack of models to assemble and paint, but I'd like to go back to the original fire caste colour scheme. I've got all the original codices that I owned at the end of the 90s/early 2000s, including the Tau one, but obviously, the colours mentioned in there just don't exist any more.

Does anyone know which of the current Citadel range can achieve a similar, if not the same theme? (Citadel because I already have a bunch of them)

Back at the start of the year I started a personal project where I was going to purpose build, from the ground up, an entire game server management panel as an alternative to Pterodactyl. All in modern PHP!

This is an introduce article, but I plan to follow it up with write-ups about the actual code and work going into it!