# How does one set up a centralized Julia installation?

**URL:** <https://discourse.julialang.org/t/how-does-one-set-up-a-centralized-julia-installation/13922>\
**Category:** General Usage\
**Tags:** package, packages, package-manager, installation\
**Created:** [August 23, 2018, 8:23am UTC](https://discourse.julialang.org/t/how-does-one-set-up-a-centralized-julia-installation/13922 "2018-08-23T08:23:42Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![Orbots](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/orbots/32/3392_2.png) [@Orbots](https://discourse.julialang.org/u/Orbots)\
**Post date:** [February 1, 2019, 8:37pm UTC](https://discourse.julialang.org/t/how-does-one-set-up-a-centralized-julia-installation/13922/27 "2019-02-01T20:37:43Z")

</div>

@htwai  
Just tested with a clean user environment. set JULIA\_PROJECT = "~/.julia/environment/v1.1  
./julia/compiled is actually created. I might not have tested with the JULIA\_PROJECT env var in the previous test.

Everything looks pretty good for the admin/user pattern if you put your central depot path at the end of JULIA\_DEPOT\_PATH, I have the central depot at the end of my JULIA\_LOAD\_PATH as well.

Users should set JULIA\_PROJECT=~/.julia/environment/v1.1 or load julia with --project=~/.julia/environment/v1.1

For the admin you simply need to switch projects to point into the central repo before adding new packages. `$ julia --project=<path_to_central_depot>/environments/v1.1 `]add` away and users should be able to use them.

---

_[View the full topic](https://discourse.julialang.org/t/how-does-one-set-up-a-centralized-julia-installation/13922)._