Mechanism for passing additional options to `datasette my.db` that affect plugins
See original GitHub issueIt’s a shame there’s no obvious mechanism for passing additional options to
datasette my.db
that affect how plugins work.The only way I can think of at the moment is via environment variables:
DATASETTE_INSERT_UNSAFE=1 datasette my.db
This will have to do for the moment - it’s ugly enough that people will at least know they are doing something unsafe, which is the goal here. _Originally posted by @simonw in https://github.com/simonw/datasette-insert/issues/15#issuecomment-667346438_
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Internals for plugins - Datasette documentation
Many Plugin hooks are passed objects that provide access to internal Datasette functionality. The interface to these objects should not be considered stable ......
Read more >New Rendering Options in datasette-client - Observable
This is useful if, for example, your SQLite database as BLOB ... also load in the Leaflet.markercluster plugin for the cluster map effect....
Read more >Apply conversion functions to data in SQLite columns with the ...
sqlite-utils convert content.db articles content ... invent a new command-line mechanism for passing in additional options to the individual ...
Read more >How To Use The Noise Gate Plugin In Logic Pro - Charles Cleyn
You can follow along with any type of audio track or midi track. Here's what my vocal track looks like: You will need...
Read more >Personal search engine with datasette and dogsheep Transcript
And it coincided with my university course giving me the option to spend a ... plugin that supports the indie auth authentication mechanism....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I renamed
--config
to--setting
and changed it to work like this:Note the lack of colons.
This actually makes colons cleaner to use for plugins - I could support this:
That’s pretty elegant: each plugin gets its own namespace and can register new settings.