We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i dont want to secure a secondary container, but instead protect a served folder locally like this:
server { server_name example.com; root /var/www/web_root/; index index.html; auth_basic "Restricted"; auth_basic_user_file auth.htpasswd; }
any way we can make this happen? currently its really just a proxy (resulting in an endless loop) when started with localhost:
FORWARD_HOST=127.0.0.1
server { listen 80 default_server; location / { auth_basic "Restricted"; auth_basic_user_file auth.htpasswd; proxy_pass http://127.0.0.1:80; proxy_read_timeout 900; } }
currently i am solving it like this:
server { listen 80 default_server; auth_basic "Restricted"; auth_basic_user_file auth.htpasswd; root /usr/share/nginx/html; index index.html; }
FROM beevelop/nginx-basic-auth COPY html_files /usr/share/nginx/html COPY nginx.conf /opt/auth.conf
it works, but it would be cool if it works without local files and custom containers. Just an idea...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
i dont want to secure a secondary container, but instead protect a served folder locally like this:
any way we can make this happen? currently its really just a proxy (resulting in an endless loop) when started with localhost:
FORWARD_HOST=127.0.0.1
currently i am solving it like this:
it works, but it would be cool if it works without local files and custom containers. Just an idea...
The text was updated successfully, but these errors were encountered: