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

Providing a copy of the larger dataset in form of a release #10

Open
danielmut opened this issue Sep 2, 2022 · 1 comment
Open

Providing a copy of the larger dataset in form of a release #10

danielmut opened this issue Sep 2, 2022 · 1 comment

Comments

@danielmut
Copy link

How would you feel about providing the result of running populate.py on the database as a release?

This could simplify some use cases where the database is required, but preferred in the extended version. At the moment, one would have to grab both the smaller database and the population script from the repository and extend the database in place, which isn't ideal to say the least.

Additionally, the population script hardcodes a relative path to the database file, requiring users to rebuild your specified directory structure for the script to even work. In most cases, people have a different destination in mind, adding yet another extra step to the process

@JoshuaBehrens
Copy link

Oh, that would be really nice. This would simplify some scripts at my place so I can just download a ready dump of a big payload. I thought about adding the 30 MB sqlite db file to my repository but I don't really like to go for git lfs. Just curl-ing it from github would be great.

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

2 participants