Hosting Sqlite Databases on Github Pages (2021)
Posted2 months agoActive2 months ago
phiresky.github.ioTechstory
calmmixed
Debate
40/100
SqliteGithub PagesWebassembly
Key topics
Sqlite
Github Pages
Webassembly
The article discusses hosting SQLite databases on GitHub Pages using WebAssembly, with commenters raising concerns about compatibility and exploring alternative databases like DuckDB and ClickHouse.
Snapshot generated from the HN discussion
Discussion Activity
Moderate engagementFirst comment
48m
Peak period
8
2-4h
Avg / period
3.8
Comment distribution19 data points
Loading chart...
Based on 19 loaded comments
Key moments
- 01Story posted
Oct 29, 2025 at 11:32 AM EDT
2 months ago
Step 01 - 02First comment
Oct 29, 2025 at 12:20 PM EDT
48m after posting
Step 02 - 03Peak activity
8 comments in 2-4h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 30, 2025 at 5:45 AM EDT
2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45748186Type: storyLast synced: 11/20/2025, 8:42:02 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
>> phiresky/sql.js-httpvfs: https://github.com/phiresky/sql.js-httpvfs
>> mmomtchev/sqlite-wasm-http: https://github.com/mmomtchev/sqlite-wasm-http
>> This project is inspired from @phiresky/sql.js-httpvfs but uses the new official SQLite WASM distribution
duckdb/duckdb-wasm: https://github.com/duckdb/duckdb-wasm
electric-sql/electric: https://github.com/electric-sql/electric :
> Specifically, Electric is a read-path sync engine for Postgres. It syncs data out of Postgres into ... anything you like. The core sync protocol is based on a low-level HTTP API. This integrates with CDNs for highly-scalable data delivery.
electric-sql/pglite: https://github.com/electric-sql/pglite :
> Embeddable Postgres with real-time, reactive bindings.
"Using Postgres for Everything" https://news.ycombinator.com/item?id=40420474
[1] - https://mrtimo.github.io/spokane-co-biz/#/model/businesses/e... [2] - https://github.com/aszenz/data-explorer
1. https://bugzilla.mozilla.org/show_bug.cgi?id=1874840
There is a second layer to the bug in that github pages should almost certainly not be sending back slices of compressed files even if gzip is listed before identity and some change to something in the github stack probably exposed the bug that was there in firefox all along.
I literally just stumbled on this last week while doing a side project that involved browser range requests so this is fresh in my head.
1. it comes down to whether it was meant that 'Accept-Encoding:identity' should be appended to the list of header values possibly overwriting the one that already was there or if 'identity' should be appended to the list of values already in the 'Accept-Encoding' header. Firefox does the latter, everyone else does the former.
https://github.com/seligman/podcast_to_text/blob/master/sear...
In my case, loading the entire file is loading a tiny bit more data, so this fallback doesn't hurt, but it's still annoying, and broke any hope I had of doing something more clever with the dataset.
its interesting, but it is not robust and I very much doubt it will have the claimed benefit for lasting without further work. At the very least its more work and requires cross browser testing.
It seems a lot of effort just to avoid paying a small amount a month for a VPS. Its free and " I forget about the backend and stop paying for whatever VPS it was on" stops being a problem (although running all the little things you have on one VPS would also simplify that).
>(or IPFS or any static file hoster)