Create a demo vagrant setup with working examples of config.json

[patcon]

Took me awhile, but I just got my setup working for apps-per-subdomain. I'll try to put together a vagrantfile that we could toss in an examples/ directory if you're interested :)

I know you haven't made a big deal of publicizing this project, but it might save someone else some time. And hey, it makes it all the easier to show someone how they might be able to use it for their org

[tizzo]

Yeah, I've been thinking I should really get some examples in there.
Vagrant would be a great way to do it. Maybe spin up a few dumb phony
node webapps as end points?

On Tue, Feb 4, 2014 at 12:39 PM, Patrick Connolly
notifications@github.comwrote:

Took me awhile, but I just got my setup working for apps-per-subdomain.
I'll try to put together a vagrantfile that we could toss in an examples/directory if you're interested :)

I know you haven't made a big deal of publicizing this project, but it
might save someone else some time. And hey, it makes it all the easier to
show someone how they might be able to use it for their org

Reply to this email directly or view it on GitHubhttps://github.com//issues/3
.

[patcon]

Was actually just going to keep it as stupid as possible with "It works!" index.html files via apache on a separate VM from the proxy, complete with some firewall rules. Thoughts?

(Tempted to use this as an opportunity to try out ansible, but will probably stick with chef :)

[tizzo]

Multiple-VMs would illustrate what you can do but would also make it a lot heavier. Multiple hosts with hostname rewrites would definitely show things off, I'm inclined to also show off mapping to multiple ports - that was my actual use case - one auth system all over SSL on 443 mapping to multiple daemons on different ports sitting behind.

[tizzo]

Also, it might be nice to show off an autossh setup - that's how I secure communication between auth-proxy and a service on another server most of the time if it isn't on an un-sniffable local private LAN.