First of all, thank you for this wonderful project :smile:
I started to use dogsheep to make my personal data searchable, and by using the project I noticed an issue with the index command.
It always expects you are running it from the root folder from where the data is located, so I got some errors while trying to make it work on my setup.
Before, I configured dogsheep.yml to add the data folder to its path like this:
data/twitter.db:
tweets:
sql: |-
...
And running the index command like this:
dogsheep-beta index data/dogsheep.db dogsheep.yml
It worked to the normal search feature with no problem this way, but when I started adding display_sql rules the app started to crash, because at datasette get_database it was looking for data/twitter and it only had a db called twitter there.
Hi,
First of all, thank you for this wonderful project :smile:
I started to use dogsheep to make my personal data searchable, and by using the project I noticed an issue with the index command.
It always expects you are running it from the root folder from where the data is located, so I got some errors while trying to make it work on my setup.
I separate all databases inside a
data
folder (I published my setup to be easier to follow: https://github.com/humrochagf/my-dogsheep)Before, I configured
dogsheep.yml
to add the data folder to its path like this:And running the index command like this:
It worked to the normal search feature with no problem this way, but when I started adding
display_sql
rules the app started to crash, because at datasetteget_database
it was looking fordata/twitter
and it only had a db calledtwitter
there.So my workaround to that was to cd into the data folder and run the indexer. You can check the way I'm doing it at this line of the makefile: https://github.com/humrochagf/my-dogsheep/blob/main/makefile#L3
It works but it would be nice to have an option to pass the path where the data is located to the index function.