Eleventy 🎈 v4.0.0-alpha.4
boosted
d@nny disc@ mc²
and 1 other
boosted
It’s been a long time since I wrote a blog post rather than a talk - but in architecting Fermyon Wasm Functions and our Wasm platforms to run “anywhere” - I spent a lot of time thinking about “minimal” platform footprints… and made some interesting discoveries. Mostly that #SQLite is still pretty awesome.
It’s been a long time since I wrote a blog post rather than a talk - but in architecting Fermyon Wasm Functions and our Wasm platforms to run “anywhere” - I spent a lot of time thinking about “minimal” platform footprints… and made some interesting discoveries. Mostly that #SQLite is still pretty awesome.
Simple tech stacks are great for resilient and maintainable systems. Why reach for #Valkey / #Redis when you can avoid introducing another dependency by implementing caching with #SQLite triggers?
This was a fun #WebDev experiment and made me even more impressed with how capable this database is for mid-sized websites and apps.
What's your favourite example of #Minimalist#Tech?
https://samuelplumppu.se/blog/using-sqlite-triggers-to-boost-performance-of-select-count
🚨 SurrealDB is sacrificing data durability to make benchmarks look better
｢ TL;DR: If you are a SurrealDB user running any SurrealDB instance backed by the RocksDB or SurrealKV storage backends you MUST EXPLICITLY set SURREAL_SYNC_DATA=true in your environment variables otherwise your instance is NOT crash safe and can very easily corrupt ｣
Unlike me from 10 years ago, I don't place a lot of value on "cutting-edge" tech anymore.
Something that works reliably and stays stable for decades without significant changes or re-learning required is what I appreciate now.
Bonus points for performance and security improvements under the hood without changing the interface.
We are VERY excited about all the features landing in the next release! However, we’re also introducing one big breaking change—and that’s the purpose of this post. WE ENCOURAGE EVERYONE USING BADGEFED TO CREATE A DATABASE BACKUP BEFORE UPGRADING.
(GO, do it now, we will wait for you and then continue reading this post.)
Don’t worry: if you forget, chances are you won’t lose data, but recovery may be trickier. If you can, please back up first.
Summary (read before upgrading)
- Database filenames now match your domain, for example:
mydomain.db. The previous single default filename is no longer used by default. - Back up your existing SQLite file NOW. You can also download a backup from the admin portal: Admin > Database > Download Backup.
- After upgrading to 0.1.1, the app uses a per-domain database. Use the import utility to migrate from your backup—or copy your backup into the data directory and rename it to the domain-based filename.
- Prefer one shared database? Set the environment variable
SQLITE_DB_PATHto your desired (or current) filename (for example,badgefed.db).
If you already upgraded without preparing
- Your previous database was not replaced or deleted. Locate your old
badgefed.db(or backup), copy it to the data directory, and rename it to the new domain-based filename.
The 0.1.1 release and full release notes are coming soon!
Badge up!
You can read the article "BadgeFed 0.1.1 — Breaking change: per-domain database filenames" by @mapachehere as well.
#badgefed #fediverse #openbadges #update #activitypub #sqlite #federation
Emelia 👸🏻
and 2 others
boosted
Hey Fediverse! 👋
We’ve been quiet… but not idle. Forget waiting for long blog posts, time for micro updates.
Today’s news:
We’ve got a few BadgeFed instances live and federating! 🏅
To make it happen, we did a hardcore backend rewrite to support multiple domains on a single machine.
For most, it’s a niche cost-saving move, but it might be useful for others too. Under the hood: each domain runs its own SQLite DB, with backups in place.
But this isn’t just about the tech, the fun part is seeing multiple BadgeFed servers talking to each other (!!). Follow them, check the thread, boost it, and watch for more as they come online!
You can read the article "BadgeFed Update: Multiple Instances Online!" by @mapachehere as well.
#badgefed #fediverse #openbadges #update #activitypub #sqlite #federationHey Fediverse! 👋
We’ve been quiet… but not idle. Forget waiting for long blog posts, time for micro updates.
Today’s news:
We’ve got a few BadgeFed instances live and federating! 🏅
To make it happen, we did a hardcore backend rewrite to support multiple domains on a single machine.
For most, it’s a niche cost-saving move, but it might be useful for others too. Under the hood: each domain runs its own SQLite DB, with backups in place.
But this isn’t just about the tech, the fun part is seeing multiple BadgeFed servers talking to each other (!!). Follow them, check the thread, boost it, and watch for more as they come online!
You can read the article "BadgeFed Update: Multiple Instances Online!" by @mapachehere as well.
#badgefed #fediverse #openbadges #update #activitypub #sqlite #federation
#MultipathTCP on #Linux. I'm not expert enough to know how exactly that works or what it's doing, but it seems to be making one of the protocols on the bedrock of the #Internet more resilient, which is always a good thing 📡
https://nlnet.nl/project/MPTCP-C-Flag/
🧵 2/n
rust-query, a library with a better API to query #SQLite databases with #Rust
https://nlnet.nl/project/rust-query/
While that sounds relatively mundane, it's something I'm excited about because Rust really doesn't have as many options as, say, Python, where I just define a model in the code and it automagically generates tables, migrations, and everything in between. Did I say doesn't have options? Well, that was only until now 😉
🧵 3/n
Alright, folks, who can make a case for using SQLite in production for small hobby sites?
The idea sounds silly to me, but I've been conditioned to consider it solely as a development tool.
Now I wonder: Does this attitude do SQLite dirty?
Michael Dexter
boosted
Been trying to keep my #PCEngines#ALIX boards alive, but it looks like #NanoBSD in #FreeBSD doesn't work (compile error in tz!) ... which is a real shame; I want to use these extremely reliable, low-power SBCs as #ZabbixDietPi, etc.
... which is a real shame; I want to use these extremely reliable, low-power SBCs as #Zabbix Proxies (using memory-backed #SQLite for the DB), but this seems to be a realllllllly big lift :(
@dexter is this something #OccamBSD can help me with? No chance of a 14.3 serial-console image out there?
Been trying to keep my #PCEngines#ALIX boards alive, but it looks like #NanoBSD in #FreeBSD doesn't work (compile error in tz!) ... which is a real shame; I want to use these extremely reliable, low-power SBCs as #ZabbixDietPi, etc.
... which is a real shame; I want to use these extremely reliable, low-power SBCs as #Zabbix Proxies (using memory-backed #SQLite for the DB), but this seems to be a realllllllly big lift :(
@dexter is this something #OccamBSD can help me with? No chance of a 14.3 serial-console image out there?
Michael Dexter
and 1 other
boosted
SQLite is a remarkable piece of software and I've always been curious about the system and the project. Here are several little known facts about SQLite.
I've used #MySQL before (last time was 2016, I think), but today I'm mostly onto #Postgres (and sometimes, #SQLite). I know PG is superior to MySQL is pretty much all aspect I could think of, but still, it seems that MySQL still has a quite big user base.
What's the catch? What am I missing here? Why would someone use MySQL over Postgres to build smt since Postgres [apparently] is better than MySQL in every single possible aspect?
It's a honest question. Please help me understand it – and perhaps, consider modern MySQL/MariaDB in next projects. :)