Deployment HOWTO? about doorman

[ahammond]

Or just https request -> doorman -> foo where doorman handles the https, too.

[sumeetp102]

It doesn't look like you need nginx b/c it is a proxy as well?

[mnutt]

Yes, doorman can handle both http and https and doesn't need nginx in front of it. When doorman was released, nginx didn't have websockets support so couldn't be placed in front of it; now it can but it's still a potentially more complicated setup.

[ahammond]

Ok, so... my setup should be https request -> doorman -> foo. Is there an example setup like this? A document that demonstrates the very basics of getting this up and running would really help.

[sumeetp102]

There is the conf.example.js. It's got a basic setup of how to do this. I'm not sure how to add multiple hosts (ie, listen on 443 and then redirect based on hostname) or where to put certs for https but the basic conf.js (which you will make a copy of conf.example.js) file will at least get you http to a single server w/ oath.

Oh, and then when the file is ready just run node /path/to/app.js

[mnutt]

I'll work on putting together a guide to better explain the setup process.

I haven't done a lot of work on the multiple virtualhost side of things because unfortunately IIRC Github will only let you use one domain per app so it would require a lot of configuration and multiple Github app keys.

[ahammond]

@mnutt that'd be fantastic! I expect there to be substantial configuration, and I expect there to be multiple GH app keys, but just getting this working at all would be a big win for me. As an aside, something like the nginx model for configs where I can include a directory (one file per service / app I'm publishing) would be a huge win. My goal is to have this as a saltstack formula that is trivial to apply to pretty much any app.