Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

refactor: Always start devsevices unless a specific URL or port has been specified. #304

Merged
merged 1 commit into from
Oct 28, 2024

Conversation

michael-simons
Copy link
Contributor

This closes #299 and I think in the long run, developer experience will be better.
Until this change we used any locally running Neo4j instance reachable on 7687.
While this is helpful when working on it from other programs, it might not be so helpful in terms of

  • the general dev experience ("Why doesn't it bring something up, I did not configure it elsewise?")
  • one doesn't notice it didn't startup anything separate and an integration tests nukes some production data on 7687

The old behaviour can easily be recreated by either specifiying the localhost:7687 Neo4j uri via quarkus.neo4j.uri or
if this doesn't work for reasons, point the fixed bolt port in devservices to the locally running instance like this
quarkus.neo4j.devservices.bolt-port=7687.

We do consider this a breaking change and will bump the version of Quarkus Neo4j from 4.4 to 5.0, which will be inline with further planned features.

…een specified.

This closes #299 and I think in the long run, developer experience will be better.
Until this change we used any locally running Neo4j instance reachable on 7687.
While this is helpful when working on it from other programs, it might not be so helpful in terms of

* the general dev experience ("Why doesn't it bring something up, I did not configure it elsewise?")
* one doesn't notice it didn't startup anything separate and an integration tests nukes some production data on 7687

The old behaviour can easily be recreated by either specifiying the localhost:7687 Neo4j uri via `quarkus.neo4j.uri` or
if this doesn't work for reasons, point the fixed bolt port in devservices to the locally running instance like this
`quarkus.neo4j.devservices.bolt-port=7687`.

We do consider this a breaking change and will bump the version of Quarkus Neo4j from 4.4 to 5.0, which will be inline with further planned features.
@michael-simons michael-simons merged commit 2d5b696 into main Oct 28, 2024
1 check passed
@michael-simons michael-simons deleted the issue/299 branch October 28, 2024 09:49
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Devservices won't start a container if you have one running @ localhost:7687
1 participant