-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
Installation instructions for existing Redis and Elasticsearch instances #49
Comments
What do you mean by already existing? Just use the same image and create another instance for tube archivist. Or maybe I don't understand what you are trying to do. |
For example, for services that require MariaDB, you can use a single MariaDB instance/container and simply create new databases. I already have containers running Redis and Elasticsearch. Rather than setting up another container of Redis and ES, can I simply let my existing instances of Redis and ES be used? Bear in mind this may not be possible due to how these apps work, but I wanted to see if it was possible. |
Ah OK, thanks for clarifying. For Elasticsearch: That shouldn't be a problem. I also have additional indexes in Elasticsearch that are not related to Tube Archivist. The indexes are defined here in the index_management module if you want to take a look. Tube Archivist doesn't touch anything in elasticsearch not related to Tube Archivist. The index name are prefixed with For Redis, first, just to make sure, Tube Archivist requires RedisJSON, that's not interchangeable with standard Redis. Also there isn't really a naming convention there, so you might end up with two application overwriting each other with their own values. So for Redis, you are better off to spin up another dedicated container to avoid that. |
Thank you for your help |
Hello,
Can directions be provided for how to integrate with already-existing Redis and ES instances? Thank you.
The text was updated successfully, but these errors were encountered: