You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 25, 2023. It is now read-only.
I have zfswatcher's web service listening on 127.0.0.1:28372, with Apache mod_proxy catching at http://server/zfswatcher and sending requests through to the zfswatcher service. This is primarily for security (SSL, etc).
At the moment, the only way to achieve this is by editing the templates in /usr/share/zfswatcher/www/templates; and prefixing "/zfs" to all the URLs. While this works fine for my, I figured others might be doing something similar.
It would be great if we could have an option in zfswatcher.conf, perhaps called something like "webroot", which specifies the prefix/directory the web service should use.
The text was updated successfully, but these errors were encountered:
I have zfswatcher's web service listening on 127.0.0.1:28372, with Apache mod_proxy catching at http://server/zfswatcher and sending requests through to the zfswatcher service. This is primarily for security (SSL, etc).
At the moment, the only way to achieve this is by editing the templates in /usr/share/zfswatcher/www/templates; and prefixing "/zfs" to all the URLs. While this works fine for my, I figured others might be doing something similar.
It would be great if we could have an option in zfswatcher.conf, perhaps called something like "webroot", which specifies the prefix/directory the web service should use.
The text was updated successfully, but these errors were encountered: