Our organization uses Sonatype Nexus to manage artifacts, whether they're internally-hosted stuff we've developed, or proxies to other repositories like Apache or similar. Most stuff is JAR-based.
我们的组织使用Sonatype Nexus来管理工件,无论它们是我们开发的内部托管的东西,还是Apache或类似的其他存储库的代理。大多数东西都是基于JAR的。
My group does most of its work in R, and we're wondering whether it makes sense to 1) deploy our internal code as R packages in Nexus, and 2) create a proxy to a CRAN mirror in Nexus. I guess this would take some glue code, but I'm not very cozy with Nexus, so I'm not really sure what that would look like. Ideally it would let us install R packages by hitting Nexus directly, rather than downloading first & manually installing afterwards.
我的小组在R中完成了大部分工作,我们想知道1)在Nexus中将内部代码部署为R包,以及2)在Nexus中为CRAN镜像创建代理是否有意义。我想这需要一些胶水代码,但我对Nexus不太满意,所以我不确定那会是什么样子。理想情况下,我们可以直接点击Nexus来安装R软件包,而不是先下载并手动安装。
Anyone have suggestions or precedent?
有人有建议或先例吗?
2 个解决方案
#1
#2
0
How about placing your internal zipped package on an (internal only, if you like) URL that you can then point the devtools::install_url function to?
如何将内部压缩包放在(仅限内部,如果您愿意)URL上,然后您可以将devtools :: install_url函数指向?
#1
2
The Nexus Community has a plugin that adds support for CRAN repositories. You can find it on GitHub.
Nexus社区有一个插件,可以增加对CRAN存储库的支持。你可以在GitHub上找到它。
#2
0
How about placing your internal zipped package on an (internal only, if you like) URL that you can then point the devtools::install_url function to?
如何将内部压缩包放在(仅限内部,如果您愿意)URL上,然后您可以将devtools :: install_url函数指向?