Overview

Neo4j is a native graph database for modelling and querying highly connected data with Cypher. DockerCP deploys it as a Docker container with persistent storage, default port mapping, domain routing, and SSL-ready configuration.

Docker image neo4j:latest
Default port 7474
Deployment type docker image
Recommended resources 2 CPU · 2 GB

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.

  1. Create or select a project where the service belongs.
  2. Review the Docker image, tag, default port, environment variables, and volume mappings.
  3. Deploy the service and check logs until the application is healthy.
  4. Attach a domain or subdomain when the application must be available publicly.
  5. Enable HTTPS and verify the final browser response.

Configuration

Environment variables

Variable Default / guidance
SERVICE_PORT 7474

Persistent volumes

Volume Mount path
neo4j_data /var/lib/data

Commands

DockerCP handles deployment from the panel, but understanding the equivalent Docker commands helps users debug services with more confidence. 

docker pull neo4j:latest
docker ps --filter "name=neo4j"

docker logs --tail=100 neo4j

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 Neo4j template: how deployment, the running service, and its key details look inside DockerCP.

Neo4j deployment form inside the DockerCP panel.
Database container with generated credentials and exposed port.
Data volume mapped so the database survives redeploys.

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.