[ckan-committers] Exposing Apache on deployments

[Adrià Mercader]

Thanks Vitor, yeah, let's change that.


Adrià

On 28 August 2014 09:11, Nigel Babu <nigel.babu at okfn.org> wrote:
> Note, we need to also change the package. Let's modify all of them at one
> go.
>
> Nigel Babu
> Developer, Open Knowledge
>
>
> On 28 August 2014 11:08, Nigel Babu <nigel.babu at okfn.org> wrote:
>>
>> +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 | @vitorbaptista
>>>
>>> The Open Knowledge Foundation
>>>
>>> Empowering through Open Knowledge
>>>
>>> http://okfn.org/  |  @okfn  |  OKF on Facebook  |  Blog  |  Newsletter
>>>
>>>
>>> _______________________________________________
>>> ckan-committers mailing list
>>> ckan-committers at lists.okfn.org
>>> https://lists.okfn.org/mailman/listinfo/ckan-committers
>>>
>>
>
>
> _______________________________________________
> ckan-committers mailing list
> ckan-committers at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-committers
>