The checked-in Compose files define the local stack: images, ports, networks, volumes, and service connections. Start with local Docker setup, then use the guide for your selected examples:
- Semoss Compose examples run published images.
- Monolith Compose examples run the locally built
local-monolithimage. - Supporting engines add optional vector databases, databases, storage, and functions.
The basic platform examples expose SEMOSS on port 9090 and PostgreSQL on 5432. The two-node examples also use 9091. Check the selected Compose file for supporting service ports and stop overlapping stacks before switching examples.
Semoss's platform and supporting-engine examples use the external network semoss-net. Monolith's local examples create their own Compose network. To use the supporting-engine examples with Monolith by container name, connect the application to semoss-net as well.
Use container names and internal ports for connections between services on a shared Docker network. Use localhost and published ports when connecting from the host. The supporting-engine networking guide lists both address forms.
The basic stack keeps PostgreSQL data and application resource directories in named volumes. MinIO variants use object storage for shared assets and persist their database and storage volumes. Inspect the selected YAML before changing volume mappings.
init.sql creates the example system databases on PostgreSQL's first initialization. Changing that script or startup credentials does not reinitialize an existing data volume. Apply database changes explicitly when keeping existing data.
docker compose -f <file> down stops the stack and retains named volumes. Adding -v deletes their data.
Rebuild local-monolith to pick up backend code changes, then recreate the application container using the selected Monolith Compose file. Its Dockerfile preserves the base image's web.xml; verify the active descriptor when testing servlet routes or filters. See developer onboarding for the build workflow.
For Kubernetes and infrastructure deployment, or semoss-artifacts property configuration, see SEMOSS-deployment.