Google Git
Sign in
apache / sling-launchpad-debian / 17a2ebe6d36226f08f2b5a6395502adbfe08d6f0
commit17a2ebe6d36226f08f2b5a6395502adbfe08d6f0[log] [tgz]
authortomekr <tomekr@unknown>Fri Apr 03 09:23:32 2015 +0000
committertomekr <tomekr@unknown>Fri Apr 03 09:23:32 2015 +0000
tree8dc1b93ea21be465433aa38adb728b69aa007674
parent02f1f36c057bda25a3fafad28705b062837626fd [diff]
SLING-4517 Add warning if there is no runmode selected. Re-enabled debian package in the contrib pom.xml. Added oak-s3 to the contrib pom.xml

git-svn-id: https://svn.apache.org/repos/asf/sling/trunk@1671021 13f79535-47bb-0310-9956-ffa450edef68
4 files changed
tree: 8dc1b93ea21be465433aa38adb728b69aa007674
  1. src/
  2. pom.xml
  3. README.md
README.md

Apache Sling debian/ubuntu packaging

This is a work in progress .deb packaging for Sling. It provides basic init.d start/stop logrotate & sample sling config. The goal is to provide a generic yet configurable sling package to eliminate the need to build sling for in-house deployments.

To run this, and install using dpkg/apt commands, review /etc/default.sling config and run “service sling start”

Components used are:

Supported run modes are:

crank           - tar files for nodes and data
crank-s3        - tar files for nodes, s3 for data
crank-mongo     - mongo for nodes and data
crank-s3-mongo  - mongo for nodes, s3 for data

Each of these are supported by building crank files using the sling-s3 module to aggregate configuration templates into usable configurations.

  • SLING_EXEC=/opt/sling - Location for all binaries & scripts.
  • SLING_CFG=/etc/sling - Tree of config file templates from which final.crantstart files are built. Editing any of these config templates triggers a rebuild of the target/crank* files.
  • SLING_DEFAULTS=/etc/default/sling - Defaults file for location & path setup and to override any of the crank settings.
  • SLING_DATA=/var/lib/sling - Local sling data dir.
  • SLING_LOG_DIR=/var/log/sling - Sling log data.

Additional bundles can be loaded in any of the defined runmodes by creating packages containing the crankstart config and dependent jars: /etc/sling/crank*/*.txt - crankstart commands required /opt/sling/contrib. - additional bundle dependencies

At start time, all /etc/sling/crank*/*.txt files are concatenated as defined by the /etc/sling/Makefile and sling is started with the runmode defined in /etc/default/sling. The init script link all the jars into one repo folder.

TODO:

  • Support clustered configurations.