Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mechanism for plugins that need a specific DB #137

Open
simonw opened this issue Jan 12, 2022 · 3 comments
Open

Mechanism for plugins that need a specific DB #137

simonw opened this issue Jan 12, 2022 · 3 comments
Labels
enhancement New feature or request research

Comments

@simonw
Copy link
Owner

simonw commented Jan 12, 2022

datasette-tiddlywiki and datasette-notebook are examples if plugins that only work if they have a particular DB file they can read and write.

In Datasette Desktop they won't start working until you've remembered to attach those DBs, and you need to do that every time you restart the app!

Need a less clunky mechanism for this.

See also Twitter: https://twitter.com/simonw/status/1481165965815541760

@simonw simonw added enhancement New feature or request research labels Jan 12, 2022
@simonw
Copy link
Owner Author

simonw commented Jan 12, 2022

This may need a new plugin hook, to allow those plugins to express their needs.

Perhaps the files get created automatically in a sensible location somewhere? But where?

@simonw
Copy link
Owner Author

simonw commented Jan 12, 2022

Solving this would unlock all kinds of exciting new plugin concepts. A Datasette TODO list for example.

@simonw
Copy link
Owner Author

simonw commented Jul 12, 2022

I could use this pattern in datasette-app-support to add a new plugin hook that those plugins could use to indicate that they need their own database created.

https://til.simonwillison.net/datasette/register-new-plugin-hooks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request research
Projects
None yet
Development

No branches or pull requests

1 participant