Overview
Deploy 9Router with persistent data plus generated dashboard and JWT secrets.
How deployment works in DockerCP
This template gives DockerCP the deployment metadata needed to create a service, prepare runtime variables, map persistent storage, expose the internal port, and connect a public domain with SSL when required.
- Create or select a project where the service belongs
- Review the Docker image, tag, default port, environment variables, and volume mappings
- Deploy the service and check logs until the application is healthy
- Attach a domain or subdomain when the application must be available publicly
- Enable HTTPS and verify the final browser response
Configuration
Environment variables
| Variable | Default / guidance |
|---|---|
NODE_ENV |
production |
DATA_DIR |
/app/data |
PORT |
20128 |
HOSTNAME |
0.0.0.0 |
JWT_SECRET |
change_me |
INITIAL_PASSWORD |
change_me |
Persistent volumes
| Volume | Mount path |
|---|---|
| 9router_data | /app/data |
Commands
DockerCP handles deployment from the panel, but understanding the equivalent Docker commands helps users debug services with more confidence.
docker pull decolua/9router:latest
docker ps --filter "name=9router"
docker logs --tail=100 9router
DNS and SSL checklist
| Step | Expected result |
|---|---|
| Add A or CNAME record | The domain points to the DockerCP server or configured target |
| Attach domain to service | The service is reachable through the selected hostname |
| Enable HTTPS | The certificate becomes active and redirect to HTTPS can be enabled |
Screenshots
Panel previews for the 9Router template: how deployment, the running service, and its key details look inside DockerCP.
Troubleshoot
- Confirm the Docker image and tag exist
- Confirm the selected internal port matches the application port
- Confirm required variables such as database URL, app URL, and credentials are set
- Check service logs after the first deployment
- Verify DNS before requesting or renewing SSL certificates