-
Notifications
You must be signed in to change notification settings - Fork 19
Rebrand from EventStore to Kurrent #828
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Deploying documentation with
|
Latest commit: |
b114212
|
Status: | ✅ Deploy successful! |
Preview URL: | https://83875d15.documentation-21k.pages.dev |
Branch Preview URL: | https://rebrand.documentation-21k.pages.dev |
1a87ef7
to
473250b
Compare
docs/clients/grpc/getting-started.md
Outdated
@@ -96,7 +96,7 @@ No additional configuration is needed having Rust installed. Go check [https://r | |||
### Connection string | |||
|
|||
Each SDK has its own way of configuring the client, but the connection string can always be used. | |||
The EventStoreDB connection string supports two schemas: `esdb://` for connecting to a single-node server, and `esdb+discover://` for connecting to a multi-node cluster. The difference between the two schemas is that when using `esdb://`, the client will connect directly to the node; with `esdb+discover://` schema the client will use the gossip protocol to retrieve the cluster information and choose the right node to connect to. | |||
The KurrentDB connection string supports two schemas: `esdb://` for connecting to a single-node server, and `esdb+discover://` for connecting to a multi-node cluster. The difference between the two schemas is that when using `esdb://`, the client will connect directly to the node; with `esdb+discover://` schema the client will use the gossip protocol to retrieve the cluster information and choose the right node to connect to. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hayley-jean are the connection strings still "esdb" and "esdb+discover" for 25.0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should use kurrentdb
and kurrentdb+discover
for 25.0 docs, but maybe add a note or tip box that says that esdb
and esdb+discover
is still supported?
cd69c82
to
8042120
Compare
Co-authored-by: Hayley Campbell <[email protected]>
Build FailedThe build has failed. You can review the full build logs and download the build log artifact via the workflow run details. |
Build FailedThe build has failed. You can review the full build logs and download the build log artifact via the workflow run details. |
Build FailedThe build has failed. You can review the full build logs and download the build log artifact via the workflow run details. |
Build FailedThe build has failed. You can review the full build logs and download the build log artifact via the workflow run details. |
Build FailedThe build has failed. You can review the full build logs and download the build log artifact via the workflow run details. |
Build FailedThe build has failed. You can review the full build logs and download the build log artifact via the workflow run details. |
// Create an instance of EventStoreDBClient, connecting to the EventStoreDB at localhost without TLS | ||
var settings = EventStoreClientSettings.Create("esdb://localhost:2113?tls=false"); | ||
// Create an instance of EventStoreClientSettings, connecting to the KurrentDB at localhost without TLS | ||
var settings = EventStoreClientSettings.Create("kurrentdb://localhost:2113?tls=false"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to confirm - is EventStoreClientSettings
intentional here (and further down in this file?) I've not used the rebranded clients yet, so I don't know if this has changed or not
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes! .net client haven't been rebranded yet. This will come later
// Create an instance of EventStoreDBClient, connecting to the EventStoreDB at localhost without TLS | ||
var settings = EventStoreClientSettings.Create("esdb://localhost:2113?tls=false"); | ||
// Create an instance of EventStoreClientSettings, connecting to the KurrentDB at localhost without TLS | ||
var settings = EventStoreClientSettings.Create("kurrentdb://localhost:2113?tls=false"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above
Event Store -> Kurrent EventStoreDB -> KurrentDB kurrent link update docker image org name revert past v24 names revert changes to deprecated client revert some pages where EventStoreDB made more sense giving the versioning revert rebrand clients update go version add python and go docs: Rebrand from EventStore to Kurrent (#828) Co-authored-by: Mark Morrissey <[email protected]> Co-authored-by: Hayley Campbell <[email protected]> engine: captures 404 page events (#859) engine: modify toc with feedback behavior (#863) engine: additional fix for the toc (#864) docs: change artifactId for java client (#865) Co-authored-by: anh nguyen <[email protected]>
Event Store -> Kurrent EventStoreDB -> KurrentDB kurrent link update docker image org name revert past v24 names revert changes to deprecated client revert some pages where EventStoreDB made more sense giving the versioning revert rebrand clients update go version add python and go docs: Rebrand from EventStore to Kurrent (#828) Co-authored-by: Mark Morrissey <[email protected]> Co-authored-by: Hayley Campbell <[email protected]> engine: captures 404 page events (#859) engine: modify toc with feedback behavior (#863) engine: additional fix for the toc (#864) docs: change artifactId for java client (#865) Co-authored-by: anh nguyen <[email protected]>
Event Store -> Kurrent EventStoreDB -> KurrentDB kurrent link update docker image org name revert past v24 names revert changes to deprecated client revert some pages where EventStoreDB made more sense giving the versioning revert rebrand clients update go version add python and go docs: Rebrand from EventStore to Kurrent (#828) Co-authored-by: Mark Morrissey <[email protected]> Co-authored-by: Hayley Campbell <[email protected]> engine: captures 404 page events (#859) engine: modify toc with feedback behavior (#863) engine: additional fix for the toc (#864) docs: change artifactId for java client (#865) Co-authored-by: anh nguyen <[email protected]>
Description
This PR applies the rebrand from EventStore to Kurrent
Page previews
https://rebrand.documentation-21k.pages.dev/