I am not sure I understand your meaning, webfork. The goal if I understand it is to catalogue a database of files such that the catalogue in FenrirFS is read-only; that is, you cannot thereafter move the source file or rename it. Here is what I can do with it that may or may not answer your question. I use the portable version, of course.
I create a Manual mode profile. I change the "Drop Operations" tab under environment settings to Custom so that I have some way of choosing whether a file in the database is physically there or is an alias. Alternately, Right-click-drag files into the middle-column file list to choose physical copy, physical move, or create an alias without moving the file. The difference is
Physical Move/Copy
- The file is physically in the subdirectory (under the FenrirFS executable)
\FenrirFS Storage\profilename\files
- Renaming or moving the file in the database does rename or move the actual file. Moving it outside of that directory deletes the listing in the database.
Alias
- An text alias file is created in the subdirectory
\FenrirFS Storage\profilename\files
- (you can have both aliases and real files
- The alias file has the real name and location of the file, as well as the display name that you see in the database
- If you rename or delete the alias, only the alias is renamed or deleted. The real file is NOT renamed nor deleted
Issue: the location in the alias file is hard coded, so if you do wish to move the repository of files to another drive, etc., you would either do a search/replace on those alias files, or set up a windows SUBST or junction point so that you keep the same path. You can also use relative paths in the alias files to make them relative to the executable, I've found.
I am curious whether this would help with what your goals are., or if I misinterpreted the issue.
