Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
avalanche-report
A simple self-hosted web server for creating and managing an avalanche forecast for a region, along with accepting public observations.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
I use Opensheet as the backend for storing reviews of my book. It's not CRUD, but easy enough to fetch data as JSON and display it on a website (and for free!).
Highly recommended.
https://github.com/benborgers/opensheet
Just tried it out. The script is able to handle multiple commands (GET, POST, etc) in one go, but you will have to package the payload as an array.
See https://github.com/ziolko/spreadapi/blob/master/spread-api.j...
As an example:
curl -L \
I'd like to plug PocketBase [0] for a similar use case.
Last week I was looking for a place to store random data with API access, and was looking at making a Google Sheets backend, but PocketBase was easy and didn't have a 60 rpm quota.
Deploying to a cheap VPS was very easy with CapRover.
[0] https://pocketbase.io/
I was exploring some alternatives for templating and CMSs a few days ago, and stumbled over NPR’s internal toolkit[1] for publishing articles with data, charts, visualizations, etc., and thought it was interesting that they included Google-Sheets-as-a-CMS.
1. https://github.com/nprapps/dailygraphics-next
I did something very similar with https://github.com/kellpossible/avalanche-report/ we started with Google Sheets because it allowed us to quickly iterate with data entry workflow. When paired with a server this also allowed us to generate custom charts/diagrams via the IMAGE function with a crafted URL query. Reads are cached in a local sqlite database.
We're in the process of migrating away from Google Sheets now as it's a little painful to set up and it's impossible to completely prevent users from editing the wrong fields in our use case. But it has served very well so far and would highly recommend this approach to start with for anyone!
I also used Google Sheets as a datastore backend: https://github.com/adam-p/danforth-east
It's a community association membership management thing, and I wanted the (non-technical) association board members to be able to easily inspect the data and do something useful with it if I moved away. It has mostly been successful, except that sometimes someone will manually edit the sheet and break something.
