|
<< Click to Display Table of Contents >> Raynet One > 2026.1 > Installation and Operations Guide > Raynet One On-Premises Installation and Operations Guide Deployment |
From the repository directory, start all services in detached mode (-d):
docker compose up -d
Note:
Ensure the .env file is present and populated before starting the stack.
Check the status of all containers:
docker compose ps
Expected result:
All core services are Up (and healthy if healthchecks are defined).
Validate that the platform is reachable and functioning (e.g., raynetone.example.com):
•https://DOMAIN_NAME (e.g., raynetone.example.com) loads the Raynet One UI (requires valid SSL certificate in production (trusted by browsers, e.g. Let's Encrypt).
•Keycloak endpoint is reachable at: raynetone-keycloak.raynetone.example.com (self-signed is acceptable for internal use).
•Backend API responds at raynetone-backend.raynetone.example.com (self-signed is acceptable for internal use).
•DataHub endpoint is reachable at: raynetone-datahub.raynetone.example.com (self-signed is acceptable for internal use).
•No recurring errors in logs for critical services: nginx-proxy, server-backend, keycloak, server-scheduler.
Note:
For internal testing, you can use HTTP temporarily (if enabled in compose files), but production requires HTTPS with valid certificates for all public facing endpoints.
Check logs for the most critical components first:
docker compose logs -f nginx-proxy
Then repeat as needed for:
docker compose logs -f server-backend
docker compose logs -f keycloak
docker compose logs -f server-scheduler