datasette-dateutil
datasette.io
datasette-dateutil | datasette.io | |
---|---|---|
1 | 6 | |
7 | 81 | |
- | - | |
3.6 | 8.0 | |
about 2 years ago | 7 days ago | |
Python | HTML | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
datasette-dateutil
-
What's New in SQLite 3.35
Hah, yeah PST v.s. PDT does make this harder.
At that point I'd switch to using additional custom SQL functions. I wrote a plugin called datasette-dateutil https://datasette.io/plugins/datasette-dateutil that exposes some extra functions, but it doesn't have anything useful for timezone calculations yet.
I've opened an issue: https://github.com/simonw/datasette-dateutil/issues/4
datasette.io
-
Architecture Notes: Datasette
Opened an issue exploring alternatives here: https://github.com/simonw/datasette.io/issues/109
I decided to just drop "any size" but keep "any shape".
-
How to have git pushes auto-deploy to a remote server?
Here's an example from one of my projects: https://github.com/simonw/datasette.io/blob/main/.github/workflows/deploy.yml
-
Schema on write is better to live by
I've come around to almost the opposite approach.
I pull all of the data I can get my hands on (from Twitter, GitHub, Swarm, Apple Health, Pocket, Apple Photos and more) into SQLite database tables that match the schema of the system that they are imported from.
For my own personal Dogsheep (https://simonwillison.net/2020/Nov/14/personal-data-warehous...) that's 119 tables right now.
Then I use SQL queries against those tables to extract and combine data in ways that are useful to me.
If the schema of the systems I am importing from changes, I can update my queries to compensate for the change.
This protects me from having to solve for a standard schema up front - I take whatever those systems give me. But it lets me combine and search across all of the data from disparate systems essentially at runtime.
I even have a search engine for this, which is populated by SQL queries against the different source tables. You can see an example of how that works at https://github.com/simonw/datasette.io/blob/main/templates/d... - which powers the search interface at https://datasette.io/-/beta
-
Using sqlite3 as a notekeeping document graph
I've been exploring this technique more over the past year and I really like it - https://datasette.io (code at https://github.com/simonw/datasette.io ) is a more recent and much more complicated example.
Extracting links from markdown and using them to populate some additional columns or tables at build time would be pretty straight forward.
- Ask HN: What novel tools are you using to write web sites/apps?
-
What's New in SQLite 3.35
I run SQLite in serverless environments (Cloud Run, Vercel, Heroku) for dozens of projects... but the trick is that they all treat the database as a read-only asset.
If I want to deploy updated data, I build a brand new image and deploy the application bundled with the data. I tend to run the deploys for these (including the database build) in GitHub Actions workflows.
This works really well, but only for applications that don't need to apply constant updates more than a few times an hour! If you have a constant stream of updates I still think you're better off using a hosted database like Heroku PostgreSQL or Google Cloud SQL.
One example of a site I deploy like that is https://datasette.io/ - it's built and deployed by this GitHub Actions workflow here: https://github.com/simonw/datasette.io/blob/main/.github/wor...
What are some alternatives?
datasette-dashboards - Datasette plugin providing data dashboards from metadata
datasette - An open source multi-tool for exploring and publishing data
litestream - Streaming replication for SQLite.
gomodest - A complex SAAS starter kit using Go, the html/template package, and sprinkles of javascript.
sqlite_modern_cpp - The C++14 wrapper around sqlite library
org-roam-server - A Web Application to Visualize the Org-Roam Database
litequeue - Queue built on top of SQLite
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
dqlite - Embeddable, replicated and fault-tolerant SQL engine.
headlessui - Completely unstyled, fully accessible UI components, designed to integrate beautifully with Tailwind CSS.
rqlite - The lightweight, distributed relational database built on SQLite.
SvelteKit - web development, streamlined