Live data from Hacker News

Hosting SQLite Databases on GitHub Pages (2021)

phiresky.github.io

1–10 of 21 posts

Re: Hosting SQLite Databases on GitHub Pages (2021)

#6
post #5

It would be a it more compelling if every example, at least for me, didn't return `[error: NetworkError: A network error occurred.]`

I'm assuming your using firefox, if so it's this bug[1] that basically prevents range requests from working. Basically firefox says it will accept gziped data even though it's a range request and github pages dudifly sends back an unreadable slice of a gziped file.

1. https://bugzilla.mozilla.org/show_bug.cgi?id=1874840

Re: Hosting SQLite Databases on GitHub Pages (2021)

#7
post #6
post #5

It would be a it more compelling if every example, at least for me, didn't return `[error: NetworkError: A network error occurred.]`

I'm assuming your using firefox, if so it's this bug[1] that basically prevents range requests from working. Basically firefox says it will accept gziped data even though it's a range request and github pages dudifly sends back an unreadable slice of a gziped file. 1. https://bugzilla.mozilla.org/show_bug.cgi?id=1874840

It doesn't work for me on safari either.

Re: Hosting SQLite Databases on GitHub Pages (2021)

#8
post #6

Earlier quoted context omitted.

I'm assuming your using firefox, if so it's this bug[1] that basically prevents range requests from working. Basically firefox says it will accept gziped data even though it's a range request and github pages dudifly sends back an unreadable slice of a gziped file. 1. https://bugzilla.mozilla.org/show_bug.cgi?id=1874840

It doesn't work for me on safari either.

works fine on safari desktop for me

Re: Hosting SQLite Databases on GitHub Pages (2021)

#10
post #5

It would be a it more compelling if every example, at least for me, didn't return `[error: NetworkError: A network error occurred.]`

I get "Error connecting to database: RuntimeError: abort(Error: server uses gzip or doesn't have length). Build with -s ASSERTIONS=1 for more info" from the sposorship stats site lined toand the same as you for the demo.

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).

Post reply on HN