What's your idea?
Add an environment variable (LIBRARY_BROWSE_ROOT) to the configuration such that the library creation folder picker can have a different root, instead of just "/".
What problem does it solve?
We run Zenith Hosting, which provides a managed hosting of BookOrbit. We create a folder for users to place book files in, however when they go to create libraries they see all folders in the root directory. This means that if they don't create a library in the correct folder they will encounter permission issues as only the /books folder we create is writeable (which appears as a 500 error).
This could be implemented by simply adding an environment variable which allows us to override this behaviour and set a new "root" for the file picker, so that the user does not have to see read-only folders in root that we don't want them to.
Anything else? (optional)
No response
Want to help?
Yes, I'd like to implement this
Before submitting
What's your idea?
Add an environment variable (LIBRARY_BROWSE_ROOT) to the configuration such that the library creation folder picker can have a different root, instead of just "/".
What problem does it solve?
We run Zenith Hosting, which provides a managed hosting of BookOrbit. We create a folder for users to place book files in, however when they go to create libraries they see all folders in the root directory. This means that if they don't create a library in the correct folder they will encounter permission issues as only the /books folder we create is writeable (which appears as a 500 error).
This could be implemented by simply adding an environment variable which allows us to override this behaviour and set a new "root" for the file picker, so that the user does not have to see read-only folders in root that we don't want them to.
Anything else? (optional)
No response
Want to help?
Yes, I'd like to implement this
Before submitting