Elasticsearch
-
I think dovecot has to use lucene/sole because the elastic search is only in dovecot enterprise.
-
I think dovecot has to use lucene/sole because the elastic search is only in dovecot enterprise.
@girish I found this here. Dovecot Enterprise have developed their own FTS solution that comes with the commercial version of Dovecot.
All the other referenced solutions are working with the FOSS version of Dovecot, so it says.https://doc.dovecot.org/configuration_manual/fts/
I keep pushing and hoping....:-)
-
@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 said in Elasticsearch:
Indeed, current plan is to implement Elastic search as an addon and not as an app.
Hey Grish - this sounds good, and exciting! I noticed that Elasticsearch has been on the roadmap for some time and am wondering if this is something we're likely to see in the Cloudron 6.x series, or if it's much further down the road yet?
-
@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.
-
Hey @girish - is this still on the roadmap for some time in the future? If so, do you have an idea of when it's likely to be set up?
-
I think part of the issue too is elasticsearch is incredibly demanding resource-wise
-
I think part of the issue too is elasticsearch is incredibly demanding resource-wise
@atrilahiji I know that Elasticsearch is stopped developing, from opensource into enterprise. And do we develop Elasticsearch from the latest opensource version?
-
G girish referenced this topic on
-
N nebulon referenced this topic on
-
@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 said in Elasticsearch:
@Nicolas Indeed, current plan is to implement Elastic search as an addon and not as an app.
Might be time to revisit that.
Elasticsearch is open source, again
https://www.elastic.co/blog/elasticsearch-is-open-source-again -
@robi Unfortunately that's the only full text search provider that's supported by Nextcloud…
@andreasdueren welp it's a large community, perhaps someone can be interested in making a plugin for meilisearch or similar
-
Since this looked to be unlikely to be included into cloudron, I packaged it into a custom app for myself because I need it for Nextcloud. This app will expose Elasticsearch only locally, for other apps to use. Let me know if anyone wants to help me test it.
-
Since this looked to be unlikely to be included into cloudron, I packaged it into a custom app for myself because I need it for Nextcloud. This app will expose Elasticsearch only locally, for other apps to use. Let me know if anyone wants to help me test it.
-
@andreasdueren nice, happy to give it a try, which version did you pack?
-
@andreasdueren said in Elasticsearch:
Great! Thanks for taking the initiative.
The .env file or a template is missing in the source, therefore the package.sh file fails to copy and build.
elasticsearch.yaml needs to be added to the copy command in package.sh, too
and the command "cloudron package" needs to be "cloudron build" ?
And you should use Cloudron Base Image 5.0.0 instead of 4.0.0
It is up and running now on my Cloudron and I still need to connect it with my Nextcloud.
I noticed that the Cloudron Proxy is exposing Elasticsearch (protected by username and password from credentials.txt)
It was a bit tricky to understand where to use the curl to create the indices. Best was to execute it inside of the container (IPADDRESS 127.0.0.1)
-
@andreasdueren said in Elasticsearch:
Great! Thanks for taking the initiative.
The .env file or a template is missing in the source, therefore the package.sh file fails to copy and build.
elasticsearch.yaml needs to be added to the copy command in package.sh, too
and the command "cloudron package" needs to be "cloudron build" ?
And you should use Cloudron Base Image 5.0.0 instead of 4.0.0
It is up and running now on my Cloudron and I still need to connect it with my Nextcloud.
I noticed that the Cloudron Proxy is exposing Elasticsearch (protected by username and password from credentials.txt)
It was a bit tricky to understand where to use the curl to create the indices. Best was to execute it inside of the container (IPADDRESS 127.0.0.1)
@Kubernetes Strange, it should build fine without it, at least it is for me. Are you sure it's not just taking a little to load? I did just make your modifications and pushed those, please try again.
-
@andreasdueren said in Elasticsearch:
Great! Thanks for taking the initiative.
The .env file or a template is missing in the source, therefore the package.sh file fails to copy and build.
elasticsearch.yaml needs to be added to the copy command in package.sh, too
and the command "cloudron package" needs to be "cloudron build" ?
And you should use Cloudron Base Image 5.0.0 instead of 4.0.0
It is up and running now on my Cloudron and I still need to connect it with my Nextcloud.
I noticed that the Cloudron Proxy is exposing Elasticsearch (protected by username and password from credentials.txt)
It was a bit tricky to understand where to use the curl to create the indices. Best was to execute it inside of the container (IPADDRESS 127.0.0.1)
@Kubernetes said in Elasticsearch:
It is up and running now on my Cloudron and I still need to connect it with my Nextcloud.
In the admin notes it's talking about localhost but I think that won't work. You need the local IP of the app which you should be able to find in the logs.
I noticed that the Cloudron Proxy is exposing Elasticsearch (protected by username and password from credentials.txt)
Oops, something I need to fix.
-
@andreasdueren said in Elasticsearch:
Great! Thanks for taking the initiative.
The .env file or a template is missing in the source, therefore the package.sh file fails to copy and build.
elasticsearch.yaml needs to be added to the copy command in package.sh, too
and the command "cloudron package" needs to be "cloudron build" ?
And you should use Cloudron Base Image 5.0.0 instead of 4.0.0
It is up and running now on my Cloudron and I still need to connect it with my Nextcloud.
I noticed that the Cloudron Proxy is exposing Elasticsearch (protected by username and password from credentials.txt)
It was a bit tricky to understand where to use the curl to create the indices. Best was to execute it inside of the container (IPADDRESS 127.0.0.1)
@Kubernetes said in Elasticsearch:
It was a bit tricky to understand where to use the curl to create the indices. Best was to execute it inside of the container (IPADDRESS 127.0.0.1)
I did that in the nextcloud apps terminal since I also set up the configuration there. But yes maybe good to clarify in the docs.
