Elasticsearch
-
@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 -
Updated Elastic to v9.1.5
https://git.due.ren/andreas/elasticsearch-cloudron/releases/tag/v9.1.5 -
Updated: https://git.due.ren/andreas/elasticsearch-cloudron/releases/tag/v1.0.17
- Plugins: bundle analysis-icu in the image so language-specific analyzers (incl. German) work out of the box and no longer hit runtime install failures on Cloudron’s read-only FS.
- Stability: revamped heap management to respect ES_JAVA_HEAP, custom jvm.options.d, and cgroup limits
-
@nichu42 This is honestly not super stable yet, I'm only using it for some nextcloud purposes and haven't tested it thoroughly.
-
@andreasdueren do you know if it's multi-tenant ? I think it makes sense to make elasticsearch as an addon (instead of an app). That way apps can come pre-installed/pre-configured with it. Apps and addons are very similar packaging wise. There is just some automation on top of it for backups and upgrades.
What's needed for addons is: an automated way to create (say) a username/password on the fly for a specific app. (The platform then injects these as env var in the container). If ES supports multiple stores (db/index or whatever it's called in ES world), then this username/password pair has to limit access to specific store i.e one app cannot access another app's store.
