Elasticsearch
-
@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.
-
I think I configured NextCloud the right way, but I still get no results when doing search. In the Logs of the elasticsearch container doesn't happen much. Does it need some time to start building the index?
@Kubernetes You need to manually start the index with
occ fulltextsearch:indexyou might want to test the configuration withocc fulltextsearch:testfirst -
@Kubernetes You need to manually start the index with
occ fulltextsearch:indexyou might want to test the configuration withocc fulltextsearch:testfirst@andreasdueren Great, thanks, it seems to work on my cloudron now.
-
Maybe to add that a cronjob in NextCloud App is recommended to update the index, e.g.
*/15 * * * * occ fulltextsearch:index --quiet@Kubernetes Recommended is
occ fulltextsearch:liveas per the docs -
@Kubernetes Recommended is
occ fulltextsearch:liveas per the docs@andreasdueren said in Elasticsearch:
@Kubernetes Recommended is
occ fulltextsearch:liveas per the docsThere was a cron command that ran once upon starting. @girish what was that again?
-
@Joseph I thought @service was different and there was another one. But maybe I'm wrong.
-
@andreasdueren maybe
@reboot? https://docs.cloudron.io/apps/#cron I would have preferred if it was called oneoff or startup
.
