Hi Bruce
The most basic information Sling reads is the sling.properties file which is
generally found at ${sling.home}/sling.properties. Defining the
"sling.properties“ as a system or startup property you can specify a different
location or name for that file. For example:
> $ java -jar sling.jar -Dsling.properties=/etc/defaults/sling
The next level of configurations are the OSGi configurations loaded by the
Launchpad Installer during initial installation. These files are read from the
${sling.home}/install folder and can be set by the „sling.installer.dir“ system
property. For example:
> $ java -jar sling.jar -Dsling.installer.dir='${sling.home}/installer‘
Unfortunately, this property is currently single valued and for moving
configuration into /etc it is not really suitable since that would mean moving
all initially installed bundles and configurations there.
Hope this helps
Regards
Felix
> Am 20.01.2015 um 08:19 schrieb Bruce Edge <[email protected]>:
>
> I¹d like to extend the debian packaging contrib to allow the user some
> degree of configurability in terms of things like:
> - Adding new OBR repositories
> - Setup logging preferences
> - Bundle specific configuration data
>
> My use case is to provide developers with an installable launchpad package
> that reads optional config data to seed the items above. This minimizes
> the effort to get a team up and running with a specific sling
> configuration.
>
> What are the options for seeding this type data before the initial launch,
> or, immediately after?
>
> With most apps one would provide an etc/defaults file, but in the sling
> case, I¹m not sure how the above data is stored.
>
> Would a config script that POSTs data to the servlet be appropriate for
> this case?
>
> How does one configure new OBR repos non-interactively?
>
> -Bruce
>
