Make database location configurable

[rieje]

How about an option to allow user to specify database location? I want to have the database(s) at /tmp (tmpfs on RAM) for the following reasons:

• I tend to update the database at least once when my system is running anyway, so I don't need it to be stored on disk and am completely fine with it being in volatile memory.

• Faster process of updating the database (not sure how fast, but it takes maybe 30-60 seconds for it to index my many terabytes of data on disk currently), since memory is many times faster than disk (especially for writing).

• Completely eliminates the load on the disk, which means the system won't be impacted at all during the process (in this regard). Also, updating databases on flash memory such as SSD wears the disk out faster, so this will prevent that. If done on my HDD, I can hear the disk writing quite audibly).

• Based on all these points, I can update the database as frequently as I want without much cost associated with it. This is especially useful for my workflow which requires this.

[cboxdoerfer]

I agree. So I'll probably add two options:

1. Make storing the database on disk optional
2. Make the database path configurable

[enoryw]

Is this part of the 0.3 milestone? Also patiently waiting for this feature :)

[cboxdoerfer]

@enoryw I can't promise anything, but it's very likely that this will be part of the 0.3 release.

[rieje]

@cboxdoerfer I don't know programming, is it trivial to modify this line to a custom directory like /tmp and that would work? I'm using fsearch-git from the AUR so to build from master. If that's all that's needed I can just patch it for myself.

[rieje]

Workaround is to symlink ~/.local/share/fsearch to e.g. /tmp/fsearch where /tmp/fsearch directory should be created.