Re:Show HN: Datasette – Create and publish an API for SQLite...
by simonw on Monday November 13, 2017 @07:59PM
(#15691710)
I've not considered authentication at all. If you do need that, my preferred option would be to put it behind a proxy such as nginx that can be configured to require authentication.
Re:Show HN: Datasette – Create and publish an API for SQLite...
by malingo on Tuesday November 14, 2017 @05:33PM
(#15699840)
I've had good luck with this library to use OpenID Connect with Nginx: https://github.com/pingidentity/lua-resty-openidc
Re:Show HN: Datasette – Create and publish an API for SQLite...
by toomuchtodo on Monday November 13, 2017 @09:04PM
(#15692030)
You would run this on the same VM or other compute as your SQLite database. You should still be able to perform scheduled updates (cron?) to the underlying SQLite database.
Re:Show HN: Datasette – Create and publish an API for SQLite...
by technomalogical on Tuesday November 14, 2017 @09:52PM
(#15701135)
The database is opened immutably, so my guess is you’d either make a copy and update or regenerate it from another source (a la Simon’s CSV to sqlite tool. You could have a symlink that points to the current DB
I have a sqlite DB with historical Visa data, and I want to expose it as an API (like your software does), but with API key. Not a python user here, can you tell me about the following?
1. Is it possible to put some security behind the API? So only queries with a key can access it?
2. How would I host this API? Where would the SQLite DB reside?
3. I understand the API is read-only, which is great and works for my use case! Can I also do read-writes to the database from a separate application that will keep updating the database on a nightly basis?