[ckan-committers] Exposing Apache on deployments

Vitor Baptista vitor at vitorbaptista.com
Wed Aug 27 19:19:07 UTC 2014


I was moving the Pakistan staging site earlier today, and I noticed that
our install instructions suggests that we make Apache listen on all
interfaces. This means that both DataPusher and the Apache backend is
accessible from the Internet (e.g. http://demo.ckan.org:8080 and
http://demo.ckan.org:8800). Is there any reason for this? If not, it would
be good to change them to only listen to the local interface.

This isn't a big improvement, but at least we don't expose ourselves to
possible Apache (or DataPusher) bugs.




Vítor Baptista

Developer  |  http://vitorbaptista.com | LinkedIn
<http://www.linkedin.com/in/vitorbaptista> | @vitorbaptista

The Open Knowledge Foundation <http://okfn.org>

*Empowering through Open Knowledge*

http://okfn.org/  |  @okfn <http://twitter.com/okfn>  |  OKF on Facebook
<https://www.facebook.com/OKFNetwork>  |  Blog <http://blog.okfn.org/>  |
Newsletter <http://okfn.org/about/newsletter/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ckan-committers/attachments/20140827/7646ce04/attachment-0002.html>

More information about the ckan-committers mailing list