This release is a pre-release and may not be stable for production use.
datasette-pins
Pin databases, tables, queries, and more to the Datasette homepage!
Installation
datasette-pins requires a recent 1.0 alpha version of Datasette to work.
pip install datasette>=1.0a13
Afterwards, install this plugin in the same environment as Datasette.
datasette install datasette-pins
Configuration
datasette-pins stores pins in the internal database. This database runs in-memory by default, which means your pins will be lost if you restart the server. To avoid that, start Datasette with the --internal option to specify where that database should be stored on disk:
datasette mydatabase.db --internal internal.db
datasette-pins has two permissions datasette-pins-write and
datasette-pins-read. Actors with the datasette-pins-write permissions can
pin and reorder items, while actors with datasette-pins-read permissions can
only view pinned items.
Here's an example
datasette.yaml file
where all actors can view pins, but only the root actor can pin items:
permissions:
datasette-pins-read:
id: "*"
unauthenticated: true
datasette-pins-write:
id: "root"
Usage
Once logged in, the root use will see new pin/unpin option under the database,
table, and query actions menu:
Development
To set up this plugin locally, first checkout the code. Then create a new virtual environment:
cd datasette-pins
python3 -m venv venv
source venv/bin/activate
Now install the dependencies and test dependencies:
pip install -e '.[test]'
To run the tests:
pytest
Building JavaScript from TypeScript
This plugin includes TypeScript/TSX source files in datasette_pins/frontend/ that need to be compiled to JavaScript. If you modify any .ts or .tsx files, you'll need to rebuild the JavaScript.
First install the Node.js dependencies:
npm install
Then build the JavaScript using just:
just js
This uses esbuild to compile and minify the TypeScript files into datasette_pins/static/.
Release files for datasette-pins 0.1a7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| datasette_pins-0.1a7.tar.gz | 34.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| datasette_pins-0.1a7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.1 kB
Release files / datasette_pins-0.1a7.tar.gz
| Download URL | datasette_pins-0.1a7.tar.gz |
|---|---|
| Size | 34.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccff76448c2adf8754f670fc77bdfb5de3903805afcbc9d5f26545b1097c8f5e
|
|
BLAKE2b-256 checksum How to use checksums |
ab3466d00c2a458c166ebe0a3b89f54907652e62ad9ebb1e0dd31a90d9e8d1f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 5, 2026.
Transparency logRelease files / datasette_pins-0.1a7-py3-none-any.whl
| Download URL | datasette_pins-0.1a7-py3-none-any.whl |
|---|---|
| Size | 33.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
edd5f62aa23bafc1b617e6a4e5c281eafd2509fa1d303ff0fa84ca6c96c9ecde
|
|
BLAKE2b-256 checksum How to use checksums |
0ce3a5292cd04d28488a29bcdeeff905020afe5421e04a896d2ad9b76b65e7ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 5, 2026.
Transparency log