Closed rmeinzer-copado closed 5 months ago
@rmeinzer-copado is attempting to deploy a commit to the FalkorDB Team on Vercel.
A member of the Team first needs to authorize it.
The update involves a simple yet significant change in the configuration template for a project. It switches the URL scheme for connecting to the database from a custom one, falkordb://
, to the standard redis://
protocol. This likely reflects a shift in the underlying database technology or a standardization effort to use more widely supported connection strings.
File | Change Summary |
---|---|
.env.local.template |
Updated FALKORDB_URL from falkordb://localhost:6379 to redis://localhost:6379 |
🐇✨
In the land of code and byte,
A rabbit hopped with sheer delight.
"A change," it said, "has come tonight,
Fromfalkordb
toredis
light."
🌟🌿
"Let's celebrate, for it's quite right,
Our data's path is now more bright!"
🎉🐰
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@gkorland please make sure the NodeJS Client supports falkordb://
urls, we've added this ability to both our Go
and Python
clients.
Description: Changing the URL protocol from
falkordb
toredis
resolves the unrecognized protocol issue from the Redis client library that FalkorDB uses.Issue: The
falkordb://
prefix on the URL is unrecognized by the Redis client, which expects the protocol to be either redis:// for unencrypted connections or rediss:// for TLS/SSL. It's causing the error:⨯ TypeError: Invalid protocol at RedisClient.parseURL (webpack-internal:///(rsc)/./node_modules/@falkordb/client/dist/lib/client/index.js:60:19)
. The error roots from theparseURL
method in theRedisClient
class of respectivenode_module
, where it specifies the required aforementioned protocols (redis:// or rediss://) and otherwise returns the 'Invalid protocol' error.Dependencies: None.
Summary by CodeRabbit