You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: