Elasticsearch
-
@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
. -
@andreasdueren maybe
@reboot? https://docs.cloudron.io/apps/#cron I would have preferred if it was called oneoff or startup .@Joseph Yup I think that was it!
-
A andreasdueren referenced this topic on
-
@girish what do you need to make this gem a official package?
@Kubernetes I don't think it's wanted because they'd prefer to make it an add-on not as an app.
-
When i look at the time this thread is open I wonder if it could be an interims solution until the add-on is ready
-
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
