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 was archived by the owner on May 29, 2021. It is now read-only.
Thanks for this container - I'd ideally use it within a docker-compose based network and not have it publicly facing at all but I'm testing out zeit.co's now tool and it only supports a single Dockerfile or package.json.
The simplest approach in my mind is to add some environment variables for a user & password that can be overridden on run/deploy. If set then we can enable auth with those details.
Is this something you'd want to support directly in this repo or are there other better approaches you can think of?
Thanks for this container - I'd ideally use it within a docker-compose based network and not have it publicly facing at all but I'm testing out zeit.co's now tool and it only supports a single Dockerfile or package.json.
The simplest approach in my mind is to add some environment variables for a user & password that can be overridden on run/deploy. If set then we can enable auth with those details.
Is this something you'd want to support directly in this repo or are there other better approaches you can think of?