HTTPS设置在刚开始启动的Artifactory-CPP-CE中被禁用 - 如何启用它?
遵循开始启动文物社区版本的说明我可以启动一个类似的文物实例:
docker run --name artifactory -d -p 8081:8081 -p 8082:8082 docker.bintray.io/jfrog/artifactory-cpp-ce:latest
之后我可以登录如http:// localhost上的Web UI中的管理员:8082。指令建议设置逆代理和在管理模块中配置反向代理,选择“ http设置”。不幸的是,这是不可能的,因为“ http设置”菜单项是灰色的:
我还不清楚为什么它是灰色的以及我能做什么来启用它。该工具提示只是说[对象对象],它似乎是一个错误,但此功能也可能不是社区版《伪影》的一部分。
Following the instructions for starting Artifactory Community Edition I can launch an artifactory instance like this:
docker run --name artifactory -d -p 8081:8081 -p 8082:8082 docker.bintray.io/jfrog/artifactory-cpp-ce:latest
Afterwards I can log in as admin in the web UI on http://localhost:8082. The instructions recommend setting up an inverse proxy and the documentation says "To configure a reverse proxy, in the Administration module, select Artifactory | HTTP Settings". Unfortunately this is not possible as the "HTTP Settings" menu item is grayed out:
It is unclear to me why it is grayed out and what I can do to enable it. The tooltip just says [object Object] which seems like a bug, but it is also possible that this feature is just not part of the Community Edition of Artifactory.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
HTTP设置在《文物社区版》中不支持。
也就是说,您可能需要查看用于测试此配置和其他功能的自由层选项: https:// jfrog.com/start-free
关于[对象对象]工具提示消息,我要感谢您的屏幕截图,因为它有助于澄清问题。我已经注意到了它,并将打开修复它的任务。
HTTP Settings is not supported in Artifactory Community Edition.
That said, you may want to check out the free-tier option for testing this configuration and additional features at: https://jfrog.com/start-free
Regarding the [object Object] tooltip message, I want to thank you for the screenshot as it helped clarifying the issue. I had taken note of it and will open a task for fixing it.
首先检查是否有
no_proxy
环境变量集,它可能会影响http设置可用性(如问题67 )。而且还考虑使用
jfrog/Charts
artifactory-cpp-ce
。那将直接出现:
Check first if there is a
no_proxy
environment variable set which could influence the HTTP settings availability (a bit as in issue 67).But also consider deploying Artifactory in a Kubernetes environment (included with any Docker Desktop setup), using the
jfrog/charts
artifactory-cpp-ce
.That would come directly with: