Elasticsearch
-
Why not build it locally and deploy it?
(I wonder if the reluctance of deploying non-appstore comes from the difficulty of building an app or because it's seen as dangerous/unstable?)
@joseph 1) This approach is seperate to the common Cloudron usage
2) Updates are not automatically, but manually
3) Not everybody is able to build and install custom packages
4) It requires public space on docker.hub or a private instance of docker repo
5) the package is not optimized by the Cloudron maintainers
-
@Nicolas Indeed, current plan is to implement Elastic search as an addon and not as an app. This will help apps like Nextcloud etc have document search as well. I will move this port to Feature Requests since it's a platform level change.
If you want to use this right away, there are two approaches:
- use an external elastic search (i.e install it on a separate server and have the LAMP app access that)
- alternately, create a cloudron package and install elastic search as an app. You can install this package on
elastic.domain.comand then your app can use it directly.
@girish Perhaps the Nextcloud Talk High Performance Backend as well as the Elasticsearch could be installed together onto the same server, somehow.
There is also Manticore:
https://forum.cloudron.io/topic/9753/manticore-search-oss-fast-database-for-search-alternative-for-elasticsearch
