Skip to content

config.json in directory config mode should be settings.json #1104

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

Closed
simonw opened this issue Nov 24, 2020 · 2 comments
Closed

config.json in directory config mode should be settings.json #1104

simonw opened this issue Nov 24, 2020 · 2 comments
Labels

Comments

@simonw
Copy link
Owner

simonw commented Nov 24, 2020

Another knock-on effect of #992.

* ``metadata.json`` - :ref:`metadata` for those databases - ``metadata.yaml`` or ``metadata.yml`` can be used as well
* ``inspect-data.json`` - the result of running ``datasette inspect`` - any database files listed here will be treated as immutable, so they should not be changed while Datasette is running
* ``config.json`` - settings that would normally be passed using ``--config`` - here they should be stored as a JSON object of key/value pairs
* ``templates/`` - a directory containing :ref:`customization_custom_templates`
* ``plugins/`` - a directory containing plugins, see :ref:`writing_plugins_one_off`

@simonw simonw added the small label Nov 24, 2020
@simonw
Copy link
Owner Author

simonw commented Nov 24, 2020

Part of #1105

@simonw simonw added this to the Datasette 0.52 milestone Nov 24, 2020
@simonw
Copy link
Owner Author

simonw commented Nov 24, 2020

I'll throw an error if a config.json file is detected.

@simonw simonw closed this as completed in 33eadb8 Nov 24, 2020
simonw added a commit that referenced this issue Nov 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant