[ckan-dev] linking data in private S3 buckets

[Joel Natividad]

Hi Anton,
You may also want to look into ODI USA's CKAN Multisite project (
https://usodi.org/2014/12/08/ckan-multisite/ and
https://github.com/opendata/CKAN-Multisite).

The project aims to make CKAN cloud-friendly, and having S3 storage is
topical to the goal.  You may want to chime in as ODI is soliciting
feedback before it breaks down the project into distinct work packages for
which it will provide funding.

We were also kinda bummed when S3 support was removed, as it increases a
CKAN instance's maintenance profile.

- Joel



--
Joel Natividad
+1 347-565-5635
@jqnatividad

Ontodia, Inc.
137 Varick Street, 2nd Floor, New York, NY 10013
pediacities.com * nycpedia.com

On Wed, Dec 17, 2014 at 11:00 AM, Ian Ward <ian at excess.org> wrote:
>
> On Wed, Dec 17, 2014 at 10:21 AM, Anton Lundin <anton at dohi.se> wrote:
> > On 17 December, 2014 - Ian Ward wrote:
> >> Are you interested in contributing development in one of these
> directions?
> >
> > Yes we are. I'm currently investigating different strategies we can go
> > about in how to solve this problem for us.
> >
> > The only downside is that i probably can't motivate the upside for doing
> > this with the engineering costs it will take to clean this up and
> > abstract it to a good interface this alone, according to my guestimates.
> >
> > But if there are more people interested in solving this, we can pool our
> > resources and solve this together.
>
> How about picking up from the work that was started on s3archive?
>
> I'm sure there are other people that are interested in this use case.
> Building a reusable extension to store ckan files remotely at least
> opens the possibility of not carrying 100% of the maintenance costs
> yourself. Why don't you start by creating a ticket outlining what
> you're planning to build on https://github.com/ckan/ideas-and-roadmap
> then anyone interested can jump in there.
>
> When your approach is clear it's not very hard to get the interfaces
> you need added to ckan. Join us at a few dev meetings if you have any
> questions.
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20141217/197c8792/attachment-0003.html>