-
-
Notifications
You must be signed in to change notification settings - Fork 999
Description
Describe the feature you'd like
Currently the Path item in File Info is a somewhat useless link. The path is relative to whatever device or container Stash is running in, and can't link out to a file manager due to sandboxing.
However, many users who have configured this using docker containers likely also have file browsers running in containers that could be linked to without violating the sandbox (e.g. copyparty). A minimal change to support this would be to allow changing the prefix of the path.
So if the user set their path prefix to
http://copyparty.homeserver.dev/
and the file path was
/data/foo/bar/baz.mp4
then the link would point to
http://copyparty.homeserver.dev/data/foo/bar/baz.mp4
instead of
file:///data/foo/bar/baz.mp4
A more refined approach would use substitution rather than prefixes, so you could have separate ${FilePath} and ${FileName} segments. This still wouldn't solve the full mapping problem (e.g. if /data/ was actually /stash-data/ on the host OS), but it would get a lot closer.
Describe the benefits this would bring to existing users
Stash covers most use cases for browse and categorization, but sometimes you need to get to the actual file system. This would create a quicker path to getting to somewhere the actual files could be manipulated.
Is there an existing way to achieve this goal?
This can be done client-side with userscripts, but this is a bit janky, slows loading, and is difficult to configure.
Have you searched for an existing open/closed issue?
- I have searched for existing issues and none cover the core request of my proposal
Additional context
No response