Skip to content

Conversation

iBotPeaches
Copy link
Member

Confirmed no active projects use older 3.2 redis.

Copy link
Member

@jweberst jweberst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should you just remove this and add it to the project specifically?

@iBotPeaches
Copy link
Member Author

Should you just remove this and add it to the project specifically?

I think presents an issue in the way DB have, since we have 3 projects (C-A, C-V, IQ-L) using this. Makes ports a bit rough, but will defer.

@jweberst
Copy link
Member

Should you just remove this and add it to the project specifically?

I think presents an issue in the way DB have, since we have 3 projects (C-A, C-V, IQ-L) using this. Makes ports a bit rough, but will defer.

They are all separate docker projects? Unless it has to map external, then there shouldn't be any port issues, right?

@iBotPeaches
Copy link
Member Author

Should you just remove this and add it to the project specifically?

I think presents an issue in the way DB have, since we have 3 projects (C-A, C-V, IQ-L) using this. Makes ports a bit rough, but will defer.

They are all separate docker projects? Unless it has to map external, then there shouldn't be any port issues, right?

Thats true, I don't think folks commonly are looking into redis from host. I will kill it entirely and move redis to projects with no external mapping

@iBotPeaches
Copy link
Member Author

#39

@iBotPeaches iBotPeaches deleted the redis-upgrade branch December 17, 2021 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants