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

--settings settings.json option #2087

Open
simonw opened this issue Jun 20, 2023 · 2 comments
Open

--settings settings.json option #2087

simonw opened this issue Jun 20, 2023 · 2 comments

Comments

@simonw
Copy link
Owner

simonw commented Jun 20, 2023

https://discord.com/channels/823971286308356157/823971286941302908/1120705940728066080

May I add a request to the whole metadata / settings ? Allow to pass --settings path/to/settings.json instead of having to rely exclusively on directory mode to centralize settings (this would reflect the behavior of providing metadata)

@asg017
Copy link
Collaborator

asg017 commented Jul 2, 2023

I just saw in the docs that Dasette auto-detects settings.json:

settings.json - settings that would normally be passed using --setting - here they should be stored as a JSON object of key/value pairs
Source

@adarshp
Copy link

adarshp commented Jul 14, 2023

@asg017 - the docs say that the autodetection only occurs in configuration directory mode. I for one would also be interested in the --settings settings.json feature.

For context, I am developing a large database for use with Datasette, but the database lives in a different network volume than my source code, since the volume in which my source code lives is aggressively backed up, while the location where the database lives is meant for temporary files and is not as aggressively backed up (since the backups would get unreasonably large).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants