[ckan-committers] Exposing Apache on deployments

[Nigel Babu]

+1

Let's do it.

Nigel Babu
Developer, Open Knowledge


On 28 August 2014 00:49, Vitor Baptista <vitor at vitorbaptista.com> wrote:

> Hi,
>
> 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.
>
> Thoughts?
>
> Cheers,
>
> --
>
> Vítor Baptista
>
> Developer  |  http://vitorbaptista.com | LinkedIn
> <http://www.linkedin.com/in/vitorbaptista> | @vitorbaptista
> <http://twitter.com/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/>
>
>
> _______________________________________________
> ckan-committers mailing list
> ckan-committers at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-committers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ckan-committers/attachments/20140828/fcbf10e1/attachment-0003.html>