Verify the Docker Deployment

Check That the Containers Are Ready

Before opening CEDAR in a browser, check that every application container has started and passed its health check:

cedarcli docker status

For a Docker deployment, the grouped table should contain 29 healthy, current service rows with the expected ports and zero unexplained restarts, followed by successful authentication and frontend-route checks. MISMATCH is a failure even when health is green because the container is not running the configured image set. hybrid mode expects 22 containers and additionally checks the seven routes served by native frontend processes.

If the CLI reports that no mode is configured, run cedarcli mode docker and try again. If another mode is already configured, stop it and run cedarcli mode --clear first.

Open CEDAR in Your Browser

CEDAR provides several browser applications, each at its own local HTTPS address. Those addresses all resolve to your computer, where the infrastructure nginx container is the single public entry point for the Docker deployment.

For example, a request to https://cedar.metadatacenter.orgx reaches nginx on port 443. Nginx handles the HTTPS connection, recognizes the cedar hostname, and forwards the request across the private cedarnet Docker network to the main editor frontend container. That container returns the HTML, JavaScript, and other files that your browser displays. Authentication and API requests from the application also return through the public nginx entry point to the appropriate backend containers. Compose also publishes their development ports on localhost for diagnostics, but the browser route above goes through nginx.

You can open any of the browser applications directly:

Application	URL
Main editor	https://cedar.metadatacenter.orgx/
OpenView	https://openview.metadatacenter.orgx/
Content	https://content.metadatacenter.orgx/
Monitoring	https://monitoring.metadatacenter.orgx/
Bridging	https://bridging.metadatacenter.orgx/

Log In to CEDAR

Start with the main editor. When you sign in, CEDAR sends you to the local Keycloak service at auth.metadatacenter.orgx. After Keycloak accepts your credentials, it returns you to the main editor.

The browser applications that require a sign-in share that Keycloak session. Each registers its own client in the same CEDAR realm, so opening Monitoring after signing in to the main editor does not ask you to sign in again.

The local realm provides these accounts:

Username	Password	Role
cedar-admin	Password123	Power user with all available roles
cadsr-admin	Password123	Power user with category-administration roles
my@user.com	my	Regular user
test1@test.com	test1	Regular test user
test2@test.com	test2	Regular test user

These credentials are for this local deployment only.

Infrastructure URLs

Component	URL	Local credentials
Keycloak	https://auth.metadatacenter.orgx/	administrator / changeme
Neo4j Browser	http://localhost:7474/	neo4j / changeme

The admin-tool URLs are available only after starting the optional admin stack. Their ports come from the active Docker profile: Redis Commander 8081, phpMyAdmin 8082, and Kibana 5601.