Skip to content
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

Closed
suckerfish opened this issue Oct 9, 2021 · 4 comments
Closed

Comments

@suckerfish
Copy link

Hello,

Can directions be provided for how to integrate with already-existing Redis and ES instances? Thank you.

@bbilly1
Copy link
Member

bbilly1 commented Oct 9, 2021

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.

@suckerfish
Copy link
Author

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.

@bbilly1
Copy link
Member

bbilly1 commented Oct 10, 2021

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 ta_ so for the moment this will create three indexes: ta_video, ta_channel, ta_download, future versions will most likely require more, but I'll prefix all of them with ta_. These indexes will get created automatically and also updated automatically whenever there is a required change. For now, as long as there is no naming conflict, I don't see any issue. In the future I'll setup authentication, so that could be a problem... But changes like that will be in the release notes.

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.

@suckerfish
Copy link
Author

Thank you for your help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants