Ticket #402 (new task) — at Version 3
Write archival/caching worker
Reported by: | pudo | Owned by: | pudo |
---|---|---|---|
Priority: | critical | Milestone: | ckan-v1.3 |
Component: | ckan | Keywords: | |
Cc: | Repository: | ||
Theme: |
Description (last modified by rgrp) (diff)
Write a worker that scans all packages in a ckan instance and uploads the data to storage.ckan.net or another suitable storage system.
- Naming scheme?
- Bucket: {ckan-instance-id}-{package-name}? {ckan-instance-id}-{package-id}?
- What happens if names change
- File: filename? hash?
- Bucket: {ckan-instance-id}-{package-name}? {ckan-instance-id}-{package-id}?
- Store hash back on ckan instance?
The caching worker will consumer update notifications and fetch packages.
Extra points for:
- Properly checking for source file modification (Last-modified, Etag)
- Using PIP VCS Backends for retrieval
- OFS/S3 Storage
Note: See
TracTickets for help on using
tickets.