You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on this Discord Support Post and this Reddit post, there is an issue with the instructions provided since they are for the rejson iteration of the container, not the replaced redis-server-stack. The server stack version has a different flag for changing the custom ports that are used.
From the Discord post:
In general, we have two methods for modifying the accessible port to the redis server: 1. Change the forwarded port
Including the port forward (- 6380:6379) will allow this to forward the internal server connection to the host's port 6380.
The other modification that is required with this is updating the REDIS_HOST for the tubearchivist container to match the host system, rather than the archivist-redis internal Docker resolver name. 2. Change the redis server port
Add the REDIS_PORT environment variable to the tubearchivist container, but do not change the REDIS_HOST.
Add the REDIS_ARGS environment variable to the archivist-redis container configuration. This will add the --port 6380 flag to the options.
For the second one, an example modification of yours to that would look like this:
Nothing else should require changes. This should allow redis to start up on port 6380, TA should then be able to access it via the internal Docker resolution addressing, and it should be good to go from there.
You should see a line similar to this relatively soon after the Redis is Starting line:
8:M 10 May 2024 10:33:23.285 * Running mode=standalone, port=6380.
The text was updated successfully, but these errors were encountered:
Based on this Discord Support Post and this Reddit post, there is an issue with the instructions provided since they are for the
rejson
iteration of the container, not the replacedredis-server-stack
. The server stack version has a different flag for changing the custom ports that are used.From the Discord post:
The text was updated successfully, but these errors were encountered: