I¹ve read through the list¹s posts on the provisioning-model, but I¹m
missing some fundamentals.
What¹s the relationship between crankstart and the provisioning-model?
At first glance they appear to provide a similar mechanism to bootstrap a
sling configuration, albeit using a slightly different configuration
syntax.
IIUC, the launchpad now uses provisioning model¹s:
launchpad/builder/src/main/provisioning/*.txt files
instead of the old:
builder/src/main/bundles/list.xml
to specify a configuration?
Crankstart is run form a jar and loads bundles specified in the file
provided on the command line.
How is the equivalent provisioning-model started from the command line?
Specifically, if the launchpad is now using the provisioning-model, can
the config file be specified on the command line ala crankstart, or does
one need to build a custom launchpad/builder and bake the startup config
into the jar?
Or, is *that* the main differentiation, launchpad provides a baked-in
startup config whereas crankstart read it from a config file at boot time?
Any suggestions for converting over to the provisioning-model for existing
contrib modules (like the Sling-S3 module) that were depending on the
https://svn.apache.org/repos/asf/sling/trunk/launchpad/builder/src/main/bun
dles/list.xml
to obtain the default startup configuration?
Should this be extracted from
launchpad/builder/src/main/provisioning/*.txt now?
Or, conversely, could the sling-s3 module be simply be folded into the
provisioning model by extending the boot.txt [settings] statement:
[settings]
sling.run.mode.install.options=jackrabbit,oak|oak_tar,oak_mongo,oak_tar_s3
,oak_mongo_s3
and providing the additional artifact/runmodes in oak.txt? That seems
highly preferable to managing sling-s3 as a separate module from the rest
of the provided boot-time config options.
I also need to fix the contrib/launchpad/debian package to use this as
well. It¹s broken right now without the builder/src/main/bundles/list.xml
to use for the bootstrap config.
-Bruce
