This repository contains the sources for building some starters that allow you to try out or use the public parts of the Composum suite - both as Docker images and as Sling Starter JAR with preinstalled Composum Nodes, Platform, Pages, Assets and ChatGPT-Intergration.
- feature/nodesstarter: A Sling Starter 12 with composum nodes installed in the newest version, and some provisions to install packages ( see feature/README.md), and run it offline. Download it [on mvnrepository.com](https://mvnrepository.com/artifact/com.composum.platform. features/composum-launcher-feature-nodesstarter) / on search.maven.org
- feature/composumstarter: Extends the feature/nodesstarter with all public Composum modules. (There are some enterprise modules, which aren't contained.) Download it on mvnrepository.com / on search.maven.org - e.g. as the oak_tar-launcher.jar , and start it with java -jar.
This module creates a couple of docker images with which it is easy to run the public parts of the Composum suite. All images are available for amd64 (Intel) and arm64 (Mac M1/M2) architectures.
-
featurelauncher: docker image composum/featurelauncher-nodes using the feature launcher, deploying a snapshot of Sling Starter 12 and preparing for further deployments both as feature archives and as packages from the filesystem.
-
composumlauncher: docker image composum/featurelauncher-composum with a sling feature launcher that launches a FAR from a Sling Starter 12 and includes all public Composum modules as features. Based on the featurelauncher docker image ( composum/featurelauncher-nodes ).
Run as a temporary installation (after stopping the container all data is deleted):
docker pull composum/featurelauncher-composum:latest
docker run --rm -p 8080:8080 composum/featurelauncher-composum:latest
Alternatively, you can also use tag develop instead of latest to use a later snapshot.
Compare the docker run documentation for other options. Composum Pages is accessible at http://localhost:8080/bin/pages.html one or two minutes after starting.
Do a mvn clean install on everything and start in the corresponding directory
using docker-compose:
docker-compose up --force-recreate -V --abort-on-container-exit
Stop it and destroy created containers with:
docker-compose down --rmi local -v --remove-orphans
Do a mvn clean install on everything and start in the corresponding directory
using docker-compose:
docker-compose up --force-recreate -V --abort-on-container-exit
Stop it and destroy created containers with:
docker-compose down --rmi local -v --remove-orphans
The following maps out most of the dependencies of the folders / docker images. The node labels contain in the first line the groupid, second the artifactid, fourth folder and fourth line the docker image name on dockerhub.
graph LR
D["com.composum.platform.features\ncomposum-launcher-feature-composumstarter\n./feature/composumstarter"]
D --> E["com.composum.platform.features\ncomposum-launcher-feature-nodesstarter\n./feature/nodesstarter"]
I["com.composum.platform\ncomposum-launcher-docker-composumlauncher\n./docker/composumlauncher\ncomposum/featurelauncher-composum"] --> D
I --> J["com.composum.platform\ncomposum-launcher-docker-featurelauncher\n./docker/featurelauncher\ncomposum/featurelauncher-nodes"]
J --> E
M["com.composum.platform\ncomposum-startup-featurelauncher\n./startup/featurelauncher"]
- startup: some experiments how to start up Sling with composum using the various starters.