issue_comments: 1683440597

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions issue performed_via_github_app
https://github.com/simonw/datasette/issues/2143#issuecomment-1683440597 https://api.github.com/repos/simonw/datasette/issues/2143 1683440597 IC_kwDOBm6k_c5kV0PV 9599 2023-08-18T06:54:49Z 2023-08-18T06:54:49Z OWNER

A related point that I've been considering a lot recently: it turns out that sometimes I really want to define settings on the CLI instead of in a file, purely for convenience.

It's pretty annoying when I want to try out a new plugin but I have to create a dedicated metadata.yml file for it just to setup a single option - I'd love to have the option to be able to run this instead:

bash datasette data.db --plugin-setting datasette-upload-csvs default-database data

So maybe there's a world in which all of the settings can be applied in a datasette.yml file OR with command-line options.

That gets trickier when you need to pass a nested structure or similar, but we could always support those as JSON:

bash datasette data.db --plugin-setting datasette-emoji-reactions emoji '["😼", "🐺"]' Note that we kind of have precedent for this in datasette publish: https://docs.datasette.io/en/stable/publish.html#custom-metadata-and-plugins

bash datasette publish heroku my_database.db \ --name my-heroku-app-demo \ --install=datasette-auth-github \ --plugin-secret datasette-auth-github client_id your_client_id \ --plugin-secret datasette-auth-github client_secret your_client_secret

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 1855885427