Need to publish Neo4J console for Dev Service
See original GitHub issueDescribe the bug
When a Neo4J database stands up by Quarkus dev service, the Neo4J console(http://localhost:7474/browser) can’t be accessible since the 7474 port wasn’t published. If I run the Noe4J container manually with “–publish=7474:7474”, I can access the console.
Expected behavior
The web console can be accessible via http://localhost:7474/browser/
Actual behavior
The web console can’t be accessible via http://localhost:7474/browser/
How to Reproduce?
- Clone https://github.com/quarkusio/quarkus-quickstarts/tree/main/neo4j-quickstart
- Comment or remove all keys and values in the application.properties
- Run Quarku Dev Mode
- Access the Noe4J console via http://localhost:7474/browser/
Output of uname -a
or ver
No response
Output of java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.3.0.Final
Build tool (ie. output of mvnw --version
or gradlew --version
)
No response
Additional information
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Getting Started with Neo4j - Developer Guides
Become an expert Neo4j developer with these introductory tutorials and guidelines that cover the entire development lifecycle, from download to deployment.
Read more >Setup Neo4j Service to run with different service ID
First step is to edit the neo4j.service and change the user and group as testuser so the service can start as that user...
Read more >Windows installation - Operations Manual - Neo4j
To run Neo4j as a console application, use: <NEO4J_HOME>\bin\neo4j console . To install Neo4j as a service use: <NEO4J_HOME>\bin\neo4j windows-service install .
Read more >Neo4j Browser User Interface Guide - Developer Guides
Please launch an AuraDB Instance or have Neo4j downloaded and installed. It also helps if you have read the section on graph databases....
Read more >Using streams.publish procedure is there a way to
As we know we can publish events with key in Kafka topic e.g. kafka-console-producer --topic key-value-topic --broker-list localhost:9092 ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In several other devservices, we added the option to choose a fixed port (PostgreSQL for sure and probably others).
Probably a good idea to follow the same pattern.
I’d say that a fixed port(
7474
) would be better by default to expose the web console since devs don’t need to add any configurations inapplication.properties
. Also, if we could add the port(e.g...devservices.expose-browser.port = xxxx
), it would be even better.