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 Mar 10, 2024. It is now read-only.
Could you please add support to have the Web front-end be password protected?
I would like to access my self hosted container outside my network but I can't do that if the site is public without any password protection.
I would think a method to approach this could be:
.htaccess/.htpasswd, but I don't know how you would configure those values via Docker Environment variables
A custom HTML page that is a login form to redirect to the actual Website-Shot webpage.
A password field on the Website-Shot capture page that must be filled in and match the Docker Environment Variable: "capture_password" for the Capture to process (Or from a local config file for non-docker users).
Personally, I think Method 3 would be the least invasive.
The text was updated successfully, but these errors were encountered:
I set up the new container and it works great! Unauthorized if password is wrong, Captures if password is right.
My only recommendation would be to change it from a text box to a password box so that the password isn't visible on my screen as plain text.
Hello,
Could you please add support to have the Web front-end be password protected?
I would like to access my self hosted container outside my network but I can't do that if the site is public without any password protection.
I would think a method to approach this could be:
.htaccess/.htpasswd, but I don't know how you would configure those values via Docker Environment variables
A custom HTML page that is a login form to redirect to the actual Website-Shot webpage.
A password field on the Website-Shot capture page that must be filled in and match the Docker Environment Variable: "capture_password" for the Capture to process (Or from a local config file for non-docker users).
Personally, I think Method 3 would be the least invasive.
The text was updated successfully, but these errors were encountered: