Keeping a couple of config files for httpd/nginx should be quite easy, we could configure it optionally (with a prompt) when running the cloud-setup-management script, for instance. We can optionally also just configure a redirect rule for port 80 on the same prompt if user doesn't want proxying, that way it will be reachable both on port 80 AND 8080 :)
How about changing the 9090 port for server? any thoughts there? should be quick enough to scour through the code to find any references.. that would fix supportability for Fedora 2x and the only drawback i see is that some might need to create new firewall rules after upgrading to this :) On Tue, May 12, 2015 at 3:17 PM, Erik Weber <terbol...@gmail.com> wrote: > It's easier to maintain a playbook/cookbook/manifest than a site-config > (that rarely should change)? :-) > > -- > Erik > > On Tue, May 12, 2015 at 3:14 PM, Jeff Moody <j...@fifthecho.com> wrote: > > > Also a good idea, but would be yet another package to be > > maintained...albeit a small one. > > Might be easier to release a pair of Ansible playbooks/Chef > > cookbooks/Puppet manifests/etc. > > > > On Tue, 2015-05-12 at 15:11 +0200, Erik Weber wrote: > > > How about bundling the httpd/nginx configuration in a separate > > > optional > > > package? > > > I have no idea for a name, but it could depend on either httpd and > > > nginx, > > > and include a site config that works out of the box. > > > > > > Should work great for those who need an easy setup, and still allow > > > those > > > who set up external loadbalancers to do as before. > > > > > >
