[ckan-dev] 2 CKAN instances, 1 public and 1 private.
Ian Ward
ian at excess.org
Tue Jul 9 13:54:43 UTC 2013
It's completely implemented as an extension.
Since it uses the API it *could* be a completely separate program, but our
"portal-update" command depends on a modified version of the
changed_packages_activity_list action so that's implemented in a plugin.
There is no reason you would have to do it the same way, of course.
Ian
On Jul 9, 2013 9:47 AM, "Henrik Aagaard Sørensen" <BU1G at tmf.kk.dk> wrote:
>
> Hi Ian.
>
>
>
> That sounds great. I will try and have a look at it, but did you make an
entire new branch or could it be implemented by a single extension for use
with stable releases of CKAN?
>
>
>
> Fra: ckan-dev-bounces at lists.okfn.org [mailto:
ckan-dev-bounces at lists.okfn.org] På vegne af Ian Ward
> Sendt: 9. juli 2013 14:19
> Til: CKAN Development Discussions
> Emne: Re: [ckan-dev] 2 CKAN instances, 1 public and 1 private.
>
>
>
>
> On Jul 9, 2013 3:03 AM, "Henrik Aagaard Sørensen" <BU1G at tmf.kk.dk> wrote:
> >
> > I’m thinking of doing a setup with 2 CKAN instances. 1 public and 1
private, where the private is protected within a firewall etc.
> >
> >
> >
> > Is it possible to have the private instance pushing all its data to the
public, so people can retrieve the same data (and more) from the public as
there are on the private?
> >
>
> This sounds exactly like what we're doing for data.gc.ca.
> >
> >
> > 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?
> >
>
> We didn't go the harvester route, instead we added a paster command that
uses the activity stream and package_show actions to collect updates, and
the package_create/update/delete actions to push those changes to our
public site.
>
> You can find our code here:
> https://github.com/open-data/ckanext-canada#L380
>
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130709/18d0a77c/attachment-0001.html>
More information about the ckan-dev
mailing list