关于 Meilisearch 的使用 #6830
Replies: 5 comments 1 reply
-
|
meilisearch 启用了https呢?好像不行了? |
Beta Was this translation helpful? Give feedback.
-
|
更新:截至今日,AList (目前最新版为v3.41.0)的 Meilisearch 依赖还停留在 v0.27.0,与之对应的最新 Meilisearch 版本为 v1.9.1,无法连接至更高版本。 模板: 开箱即用: |
Beta Was this translation helpful? Give feedback.
-
我也补充一个docker-compose 文件吧,把 alist 和 meilisearch 放在一块一键启动,亲测可用 |
Beta Was this translation helpful? Give feedback.
-
|
alist 3.45.0 重建索引,会提示网络错误以及alist 登陆token失效等 |
Beta Was this translation helpful? Give feedback.
-
上面的参数看起来有点迷糊 我也补充个自己用的compose配置 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
我发现文档中对于 Meilisearch 并不是特别详细,故在项目 Discussion 部分分享一下个人的部署经验,希望能帮到后面的朋友们🌹
个人认为, Meilisearch 相比于 MySQL 和 SQLite 有巨大优势,因为我使用这两者构建索引时从来没构建完成过(),而 Meilisearch 大约耗时 15 秒就完成了。
以下为安装和配置步骤,如有纰漏,还请各位指正。
请注意,Meilisearch 默认会监听 0.0.0.0:7700。若使用 host 网络,请注意检查防火墙设置,避免外部网络访问到 Meilisearch。
{ "force": , "site_url": "", "cdn": "", "jwt_secret": "", "token_expires_in": , "database": {}, "meilisearch": { "host": "http://localhost:7700", "api_key": "刚刚生成的密钥", "index_prefix": "" }, "scheme": {}, "temp_dir": "", "bleve_dir": "", "dist_dir": "", "log": {}, "delayed_start": , "max_connections": , "tls_insecure_skip_verify": , "tasks": {}, "cors": {}, "s3": {} }例如:
{ "force": , "site_url": "", "cdn": "", "jwt_secret": "", "token_expires_in": , "database": {}, "meilisearch": { "host": "http://localhost:7700", "api_key": "c5f15904a135ebfbbcbec4d0bfd30050", "index_prefix": "" }, "scheme": {}, "temp_dir": "", "bleve_dir": "", "dist_dir": "", "log": {}, "delayed_start": , "max_connections": , "tls_insecure_skip_verify": , "tasks": {}, "cors": {}, "s3": {} }Beta Was this translation helpful? Give feedback.
All reactions