GETTING STARTED

Your first local run.

Understand the starting point before you run it. The commands below come from the README; they are not a substitute for the selected release’s build and security instructions.

1. Prepare an isolated environment.

Use the JDK and Maven versions required by your chosen release. The README gives the commands; RUNNING.md and VERSIONS.md in the repository name the exact prerequisites for the release you build.

Do not expose the starter to an untrusted network. Restrict inbound access to port 6727 with the environment’s network controls before starting. An example URL using 127.0.0.1 does not ensure that the listener binds only to loopback.

2. Build from the source root. bash

mvn clean install

Source: README.md, Quick start. Run in the chosen source checkout—not on this website.

3. Launch the TAR aggregate. bash

cd starter/platform/server
java --add-opens java.base/java.lang=ALL-UNNAMED \
  -cp "target/dependency/org.apache.sling.feature.launcher/lib/*" \
  org.apache.sling.feature.launcher.impl.Main \
  -f target/slingfeature-tmp/feature-libre-tar.json \
  -u "file://$PWD/target/artifacts" \
  -p /tmp/libre/data -c /tmp/libre/cache/artifacts

Verbatim command sequence from the README. The /tmp paths are local quick-start examples, not a production persistence recommendation. Confirm runtime flags and paths against the selected release.

4. Open the local instance.

The README uses http://127.0.0.1:6727/. Keep the environment isolated while exploring. The launcher’s -p directory is sling.home and the repository lives beneath it; do not treat the data directory like a disposable artifact cache.

5. Check the documented identity endpoint. bash

curl --user YOUR_USER \
  http://127.0.0.1:6727/api/identity/v1/me

Use a provisioned local user. curl prompts for the password. This is a read request; machine-client writes have a separate CSRF marker requirement.

6. Choose the next guide.

Read the architecture before changing storage or removing features. Read the API guide before writing integration code. Review the security guide before any broader network exposure. Public site APIs and the content module require a site-enabled assembly; they are not implied by this starter command.

A few useful answers.

Does a successful build prove the runtime is ready?

No. Feature analysis and runtime activation answer different questions. Boot the assembly and run the release’s integration and health checks.

Can I switch storage later with one flag?

No. The architecture describes separate TAR and Mongo aggregates. Moving existing content between them is a migration requiring transfer and validation.