This parses the .env file, configures the generated project to use your Aura instance, and sets neo4j_type to aura automatically.
4
Verify the connection
cd my-appmake test-connection
You should see:
✅ Connected to Neo4j Aura (neo4j+s://xxxxxxxx.databases.neo4j.io)
5
Seed data and start
make installmake seedmake start
Connection refused
Ensure your Aura instance is Running (not paused).
Free-tier instances pause after 3 days of inactivity — resume from the Aura console.
Check that NEO4J_URI starts with neo4j+s:// (TLS is required for Aura).
Authentication failed
Double-check the password in your .env file.
If you lost the password, reset it from the Aura console under Instance settings.
Slow queries
Free-tier Aura instances have limited resources — queries may take 2–5 seconds. Upgrade to a paid tier for better performance.
The generated project includes a docker-compose.yml that runs Neo4j locally in a Docker container. This is the default setup when you don’t specify --neo4j-aura-env or --neo4j-local.
While the container is running, open http://localhost:7474 to access the Neo4j Browser. Connect with:
Connect URL: neo4j://localhost:7687
Username: neo4j
Password: password
Port already in use
If port 7687 or 7474 is already in use, either stop the conflicting service or update the ports in docker-compose.yml.
Container won't start
Check Docker logs:
docker-compose logs neo4j
Common causes: insufficient memory (Neo4j needs at least 512 MB RAM) or file permission issues on the data volume.
@johnymontana/neo4j-local is an npm package that downloads and runs Neo4j Community Edition directly on your machine. It requires Node.js but no Docker installation.
All four Neo4j connection options (--neo4j-aura-env, --neo4j-local, --neo4j-uri, and the default Docker path) produce the same generated project structure. Only the .env values and neo4j_type setting differ.