Elasticsearch

[andreasdueren]

@Kubernetes You need to manually start the index with occ fulltextsearch:index you might want to test the configuration with occ fulltextsearch:test first

[Kubernetes]

@andreasdueren Great, thanks, it seems to work on my cloudron now.

[Kubernetes]

Maybe to add that a cronjob in NextCloud App is recommended to update the index, e.g.

*/15 * * * * occ fulltextsearch:index --quiet

[andreasdueren]

@Kubernetes Recommended is occ fulltextsearch:live as per the docs

[andreasdueren]

@andreasdueren said in Elasticsearch:

@Kubernetes Recommended is occ fulltextsearch:live as per the docs

There was a cron command that ran once upon starting. @girish what was that again?

[joseph]

I think like @service occ fulltextsearch:index --quiet

[andreasdueren]

@Joseph I thought @service was different and there was another one. But maybe I'm wrong.

[joseph]

@andreasdueren maybe @reboot ? https://docs.cloudron.io/apps/#cron I would have preferred if it was called oneoff or startup .

[andreasdueren]

@Joseph Yup I think that was it!

[Kubernetes]

@girish what do you need to make this gem a official package?

[andreasdueren]

@Kubernetes I don't think it's wanted because they'd prefer to make it an add-on not as an app.

[Kubernetes]

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

[joseph]

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?)

[Kubernetes]

@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