4 ms·

Author here. I really think there's a lot of value in this model for users to self-host apps. PostgreSQL can run cron jobs, operate on external data with forei

Author here. I really think there's a lot of value in this model for users to self-host apps. PostgreSQL can run cron jobs, operate on external data with foreign data wrappers, and even do some number-crunching with Madlib right within SQL. So, the user only has to manage a postgresql db, retains control on data and can easily get upgrades of webapps via CDN and mobile apps via app stores. Developers benefit because (a) there is no server-side programming language to deploy/maintain and (b) PostgREST API is very well thought-out and very predictable - leading to easier development across frontend/mobile frameworks.

klyrs 5y ago
FYI: On android/ff the site menu hovers, and takes up over a third of my screen. It's pretty annoying.
- nileshtrivedi 5y ago
  The site is made with Gitbook which seems to have gone through major changes recently. I'll see what I can do about it.
- cutler 5y ago
  Seconded.
steve-chavez 5y ago
Nice! In the past I've also rendered an OSM map[1] with this approach and as you mention caching/CDN should make it suitable for production. [1]: https://gist.github.com/steve-chavez/c1435a8c9583d2524e87e4f7c378d322 https://gist.github.com/steve-chavez/c1435a8c9583d2524e87e4f...
- nileshtrivedi 5y ago
  Pretty cool! Was the function being named "index.html", made it available on /rpc instead of /rpc/index.html ?
  - steve-chavez 5y ago
    Ah, no - PostgREST doesn't have that kind of convention builtin(default to searching an index.html on path). I'll update the gist and change the function to `map.html` to avoid any confusion.
chrismorgan 5y ago
Meta: your code blocks have the CSS `overflow: scroll`, which is wrong, causing scrollbars to appear unnecessarily; 9999⁄10000 times, `overflow: auto` is what you want instead. (macOS is the only significant desktop platform that uses overlay scrollbars by default, where the difference is not generally visible.)
- nileshtrivedi 5y ago
  I am using Gitbook. They seemed to have changed things in a big way and a number of issues seem to have cropped up. Unlikely I can fix these myself.

klyrs 5y ago

FYI: On android/ff the site menu hovers, and takes up over a third of my screen. It's pretty annoying.

nileshtrivedi 5y ago
The site is made with Gitbook which seems to have gone through major changes recently. I'll see what I can do about it.
cutler 5y ago
Seconded.

steve-chavez 5y ago

Nice! In the past I've also rendered an OSM map[1] with this approach and as you mention caching/CDN should make it suitable for production. [1]: https://gist.github.com/steve-chavez/c1435a8c9583d2524e87e4f7c378d322 https://gist.github.com/steve-chavez/c1435a8c9583d2524e87e4f...

nileshtrivedi 5y ago
Pretty cool! Was the function being named "index.html", made it available on /rpc instead of /rpc/index.html ?
- steve-chavez 5y ago
  Ah, no - PostgREST doesn't have that kind of convention builtin(default to searching an index.html on path). I'll update the gist and change the function to `map.html` to avoid any confusion.

chrismorgan 5y ago

Meta: your code blocks have the CSS `overflow: scroll`, which is wrong, causing scrollbars to appear unnecessarily; 9999⁄10000 times, `overflow: auto` is what you want instead. (macOS is the only significant desktop platform that uses overlay scrollbars by default, where the difference is not generally visible.)

nileshtrivedi 5y ago
I am using Gitbook. They seemed to have changed things in a big way and a number of issues seem to have cropped up. Unlikely I can fix these myself.