Would it work? Is there documentation available on how to setup something like 'central' on a private server, is there a mechanism to synchronize selected artifacts?
Well, you could become a mirror of central but, what's the point of grabbing ~10 GB of artifacts? You won't need all of them and the usual recommendation is to use a repository manager.
Actually my initial thoughts was:
Use a Nexus connected to the internet outside the SEE
rsync the content of this Nexus to a DVD.
Copy the content to the Nexus of the SEE via a DVD.
Repeat periodically.
I found this solution ugly but, now that we have more details on your situation, it might be an acceptable.
我们通过自动配置交换机以适当地连接和断开网络来完全自动化此过程（因此始终存在物理连接，但没有可用的 IP 连接）。也许你可以做类似的事情 - 这仅取决于“断开连接”定义的灵活性；）
I've once worked in a network environment where a portion of a network wouldn't have access to the internet or any other net. Whenever we needed to update software within this network, we did the following:
upload updated software to a "secure" host (step stone)
disconnect step stone from net
connect step stone to secure net
push updated software to repository
disconnect step stone from secure net
We fully automated this process by automatically configuring a switch to connect and disconnect networks appropriately (so there was a physical connection at all times but no usable IP connection). Maybe you could do something similar - it just depends on the flexibility of the definition of "disconnected" ;)
Ordinarily our server hosting Nexus would not be able to access the Internet. However, I met with the operations team and explained to them that allowing Nexus to automatically download artifacts from the Internet is a huge productivity win for us.
Once they understood our needs, ops allowed the server to access a very strict whitelist of Internet IPs such as the central Maven repository. So we still have to go through ops to add new repositories or perform whitelist fixes when outside repository IP addresses change. But overall we felt it was the best compromise between security and productivity and it works for us.
See if your stakeholders will go for connecting your network to the Internet in a highly restricted whitelist-only manner once you reiterate to them how doing so will make you more productive and ultimately save everybody time.
发布评论
评论（4）
好吧，您可以成为中央的镜像，但是，获取约 10 GB 的工件有什么意义？您不需要所有这些，通常的建议是使用存储库管理器。
实际上我最初的想法是：
我发现这个解决方案很丑陋，但是现在我们对您的情况有了更多详细信息，它可能是可以接受的。
Well, you could become a mirror of central but, what's the point of grabbing ~10 GB of artifacts? You won't need all of them and the usual recommendation is to use a repository manager.
Actually my initial thoughts was:
rsyncthe content of this Nexus to a DVD.I found this solution ugly but, now that we have more details on your situation, it might be an acceptable.
我曾经在一个网络环境中工作，其中网络的一部分无法访问互联网或任何其他网络。每当我们需要更新该网络内的软件时，我们都会执行以下操作：
我们通过自动配置交换机以适当地连接和断开网络来完全自动化此过程（因此始终存在物理连接，但没有可用的 IP 连接）。也许你可以做类似的事情 - 这仅取决于“断开连接”定义的灵活性；）
I've once worked in a network environment where a portion of a network wouldn't have access to the internet or any other net. Whenever we needed to update software within this network, we did the following:
We fully automated this process by automatically configuring a switch to connect and disconnect networks appropriately (so there was a physical connection at all times but no usable IP connection). Maybe you could do something similar - it just depends on the flexibility of the definition of "disconnected" ;)
我在我的环境中遇到了类似的问题。
通常我们托管 Nexus 的服务器将无法访问互联网。不过，我会见了运营团队并向他们解释说，允许 Nexus 自动从 Internet 下载工件对我们来说是一个巨大的生产力提升。
一旦他们了解了我们的需求，运维人员就允许服务器访问非常严格的互联网 IP 白名单，例如中央 Maven 存储库。因此，当外部存储库 IP 地址发生变化时，我们仍然需要通过操作来添加新存储库或执行白名单修复。但总的来说，我们认为这是安全性和生产力之间的最佳折衷方案，并且它对我们有用。
一旦您向利益相关者重申这样做将如何提高您的工作效率并最终节省每个人的时间，看看您的利益相关者是否会选择以严格限制的白名单方式将您的网络连接到互联网。
I faced a similar issue in my environment.
Ordinarily our server hosting Nexus would not be able to access the Internet. However, I met with the operations team and explained to them that allowing Nexus to automatically download artifacts from the Internet is a huge productivity win for us.
Once they understood our needs, ops allowed the server to access a very strict whitelist of Internet IPs such as the central Maven repository. So we still have to go through ops to add new repositories or perform whitelist fixes when outside repository IP addresses change. But overall we felt it was the best compromise between security and productivity and it works for us.
See if your stakeholders will go for connecting your network to the Internet in a highly restricted whitelist-only manner once you reiterate to them how doing so will make you more productive and ultimately save everybody time.
Nexus Pro 中的采购功能正是为了处理这种用例而设计的。
什么是采购？
采购套件用户指南
The Procurement features in Nexus Pro were designed exactly to handle this use case.
What is Procurement?
Procurement Suite User guide