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

Default Sqlite metadata database doesn't use configured --storage directory #29

Open
da4089 opened this issue Mar 7, 2018 · 0 comments

Comments

@da4089
Copy link

da4089 commented Mar 7, 2018

If using the --storage option, and defaulting to Sqlite database, the metadata.db file is always created as packages/metadata.db regardless of what --storage path was specified.

Using the STORAGE environment places the metadata file into the specified directory.

The reason is that the database options definition uses the default_storage path, which will default to packages unless STORAGE is set, but since the options aren't parsed yet, the --storage value is ignored.

As a user, this is a little surprising -- I'd expected STORAGE and --storage to have the same effect.

I think the best solution would be to defer constructing the database URL until after options parsing, in server.py?

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

No branches or pull requests

1 participant