Just learned a horrifying thing about PHP asserts

Here's what a full server configuration can look like

If you have serious projects on GitHub, it's a good idea to set up mirrors of your repos on other forges. Very easy to do with Gitea/Forgejo. Self-hosting Forgejo is also super easy, if you have a NixOS server you can just add it as a service and put it behind nginx like this

brew install jj jj rebase -r C --insert-before A jj rebase -r B --insert-before A

Thank you @vonderleyen, very cool!

GitHub repo:

Full article:

This is what my entire server config looks like. On NixOS, this configures: - nginx - php-fpm - SSL certificates (including renewals) - cron for Laravel schedule - users and groups - queue worker - firewall - ssh keys, and more For as many sites as I want. Article link below

The system is meant to be fully editor-based (as in an editor that can search is all you *need*) but for convenience I've also written a simple CLI tool in Rust for getting a quick look at all the TODOs within a project in a nicely structured way https://t.co/ehWilxxiY7

https://t.co/BBr6ckBJTJ

New article about a system for organizing TODOs in code that I use in pretty much every project Came up with it a few years ago while working on some brutal refactors and stuck with it since. It has worked exceptionally well in every project I've worked on

Why does ChatGPT now start every reply with "Ah, ..."

NixOS rocks

https://t.co/RqxnPjypNm

New article — some things to consider when using SQLite in production (from the point of view of Laravel apps). Covers: 1. Journal mode 2. Data types 3. Concurrent transactions (the dreaded "database is locked" error) Link below

You can see a simple demo here

As much as I love SQLite one thing that's annoying about using it with PHP in production is that it doesn't handle concurrent locks well. This really is more of a PHP limitation and one that should be imo addressed The issue is basically that there's no way to tell PDO to begin

Another cool thing you can split like this is two sets of (data) outputs I remember writing a script that was used as: ./thing > usd_output.txt 2>eur_output.txt

I'm using NixOS in production (Laravel site) and it's the single best experience I've had managing a server

One thing I like to do in custom CLI utils is separate the "real output" from any additional informative output into stdout and stderr. That way I can pipe either one into a file or even the clipboard (`| pbcopy` on macOS)