We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have read the documentation. 我已经阅读了文档。
I'm sure there are no duplicate issues or discussions. 我确定没有重复的issue或讨论。
I'm sure it's due to AList and not something else(such as Network ,Dependencies or Operational). 我确定是AList的问题,而不是其他原因(例如网络,依赖或操作)。
AList
Dependencies
Operational
依赖
操作
I'm sure this issue is not fixed in the latest version. 我确定这个问题在最新版本中没有被修复。
v3.42.0/docker:main-aio
关联issue: #5168,#4133
在个人配置没有设置密码的情况下,alist会忽视database.name项配置,数据库表均生成在postgres/public下, 也就是当前用户下 在内网使用时, postgres可以通过hba.conf设置内网ip段为trust, 从而无需密码连接。 这是一个很正常的使用场景,希望修复。
database.name
postgres/public
附上临时的解决方案: password处不为空即可, 个人测试@可以正常使用
@
暂无
"database": { "type": "postgres", "host": "postgres", "port": 5432, "user": "postgres", "password": "", "name": "alist", "table_prefix": "x_", "ssl_mode": "disable" }
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Please make sure of the following things
I have read the documentation.
我已经阅读了文档。
I'm sure there are no duplicate issues or discussions.
我确定没有重复的issue或讨论。
I'm sure it's due to
AList
and not something else(such as Network ,Dependencies
orOperational
).我确定是
AList
的问题,而不是其他原因(例如网络,依赖
或操作
)。I'm sure this issue is not fixed in the latest version.
我确定这个问题在最新版本中没有被修复。
AList Version / AList 版本
v3.42.0/docker:main-aio
Driver used / 使用的存储驱动
Describe the bug / 问题描述
关联issue: #5168,#4133
在个人配置没有设置密码的情况下,alist会忽视
database.name
项配置,数据库表均生成在postgres/public
下, 也就是当前用户下在内网使用时, postgres可以通过hba.conf设置内网ip段为trust, 从而无需密码连接。
这是一个很正常的使用场景,希望修复。
附上临时的解决方案: password处不为空即可, 个人测试
@
可以正常使用Reproduction / 复现链接
暂无
Config / 配置
Logs / 日志
No response
The text was updated successfully, but these errors were encountered: