# JuliaRegistries setup for air gapped network

**URL:** https://discourse.julialang.org/t/juliaregistries-setup-for-air-gapped-network/94313
**Category:** General Usage
**Tags:** packages, registry
**Created:** [February 8, 2023, 11:12pm UTC](https://discourse.julialang.org/t/juliaregistries-setup-for-air-gapped-network/94313 "2023-02-08T23:12:15Z")
**Posts on this page:** 1
**Showing post:** 27

<div class="post-metadata">

### Author: ![Ashlin\_Harris](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ashlin_harris/32/210166_2.png) [@Ashlin\_Harris](https://discourse.julialang.org/u/Ashlin_Harris)
#### Post date: [February 13, 2023, 8:36pm UTC](https://discourse.julialang.org/t/juliaregistries-setup-for-air-gapped-network/94313/27 "2023-02-13T20:36:23Z")

</div>

I believe it does, at least from the end user’s perspective. They can open a Julia REPL, access the package manager in offline mode, and import whichever packages they need. It doesn’t create a clone of the entire Julia registry, but that might not be needed.

Since new packages have to be added in installments, I would say this approach works best for a small number of distinct teams, which is probably the norm on air-gapped systems. Each team would probably use similar packages and could have a designated sysimage. It would be a poor fit for, say, a university of students who each want to try out various packages in the Julia ecosystem, and that’s where I think an actual clone of the registry would shine. But maintaining that would still involve periodic updates.

---

_[View the full topic](https://discourse.julialang.org/t/juliaregistries-setup-for-air-gapped-network/94313)._