Hi,
you can use the contentloader mechanism. [1]
ie, build a jar of all your content, with a MANIFEST.MF containing a
directive
Sling-Initial-Content: SLING-INF/content
Where SLING-INF/content is the path into the jar where the content
that you want loaded into / is located.
Then redeploy that jar to Sling to update the content.
An Example of a maven project that pulls about 1600 files form version
control and builds a jar[2]. If you are using the mechanism for
development you might also consider the fsresource bundle[3] in
contrib which allows you to map a local file system to a URL space.
HTH
Ian
1 http://sling.apache.org/site/content-loading-jcrcontentloader.html
2
http://github.com/ieb/open-experiments/tree/master/slingtests/osgikernel/bundles/uxloader/
3
http://sling.apache.org/site/accessing-filesystem-resources-extensionsfsresource.html
On 4 Dec 2009, at 05:53, John Crawford wrote:
Greetings,
So I came across an idea and I'm sure that it has been tackled by
the sling
dev group before. So here goes... I'm wanting to upload a ton of
content
at various points in time, images primarily. I'll have say,
500-3000 images
per upload. I know pushing files into the repo is possible through
webdav,
but I was wondering if you all had ever performed a zip file upload
and
unpacked it within the repo? (Is there already an API and set of best
practices for this?)
Respectfully,
John
