Zader

Sure, having authenticated docs is cool. But there are several things that may need a bit more thinking. 1. `passport-gitlab2` gives node server power to use oauth2. But actually, static...

How about just using a fixed user:pass pair to protect the doc and share it with your group? Is this acceptable? Any pitfall? http://nginx.org/en/docs/http/ngx_http_auth_basic_module.html

GCP uses NGINX to serve static files as well as to forward to express. So SSL should be set on NGINX. Several things to do - [ ] expose `GCP_HTTPS`...

@morph027 You can't do that this way because the projects owner are not responsible for deploying. We can't have them to set project variable to enable SSL.

See https://github.com/YuMS/gitlab-ce-pages/pull/20#issuecomment-262700198 #20 give this a try but it is not perfect, so I merged it to a non-master branch for now.