Installation instructions for existing Redis and Elasticsearch instances about tubearchivist HOT 4 CLOSED

Thank you for your help

from tubearchivist.

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.

from tubearchivist.

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.

from tubearchivist.

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.

from tubearchivist.