Closed zbruhnke closed 4 years ago
No preference, I tend to recommend the use of the vanilla Elasticsearch image provided by elastic.co.
We started publishing it out of habit, we've always provided a fusionauth-search
zip, deb and rpm bundle so that ours users didn't have to be knowledgeable of Elasticsearch. The bundle is just plain Elasticsearch.
In theory we could stop publishing the fusionauth-search
image. Once you're in the Docker world, it makes perfect sense to use the 6.3.1 image provided by elastic.co.
The main reason I haven't pulled it is because I don't know who is using it. However if I look at the pull count that DockerHub shows, I see 213k+ for fusionauth-app
and 2.2k for fusionauth-search
- so the evidence seems to indicate hardly anyone is using the fusionauth-search
image.
https://github.com/FusionAuth/fusionauth-containers/blob/88bd62b9c1eaa82a1bb3293b6f66b8c8474811ef/docker/fusionauth/docker-compose.yml#L20
Hi all,
Mostly just curious if this is the preferred use over the fusionauth-search container. It feels like having both is redundant. I have been using this with luck locally but as im settling on automating some local dev things I'm wondering why there is an fa_search container at all if this is the preferred method or vice versa.
Would be good to get an understanding of why both are here?