[ckan-dev] 2 CKAN instances, 1 public and 1 private.

[Adrià Mercader]

Just to add on the harvester option, this is something that has been
done in some deployments. Instance A (public) harvests datasets from
Instance B (private), using an API key from an authorized user from
instance B.

Have a look at the "api_key" config option:

https://github.com/okfn/ckanext-harvest#the-ckan-harvester

Adrià

On 10 July 2013 11:59, Henrik Aagaard Sørensen <BU1G at tmf.kk.dk> wrote:
> Is it possible to have the harvester extension pushing data from the internal to the public?
> Instead of having the public harvesting from the internal? (even though that kinda is against the definition of harvesting)
>
> -----Oprindelig meddelelse-----
> Fra: ckan-dev-bounces at lists.okfn.org [mailto:ckan-dev-bounces at lists.okfn.org] På vegne af Sean Hammond
> Sendt: 9. juli 2013 18:45
> Til: ckan-dev at lists.okfn.org
> Emne: Re: [ckan-dev] 2 CKAN instances, 1 public and 1 private.
>
>> I've tried to read a bit on the harvester extension, but I'm not quite
>> sure that it is intended for such a setup?
>
> The harvester is really intended for harvesting from multiple public sites into a single, big public site (something like publicdata.eu, for
> example) but I think the harvester should work just fine for your use-case as well. Ian's alternative solution is a proven one for this use-case, though.
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev