# Activating a shared named environment via JULIA\_PROJECT?
**URL:** https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975
**Category:** General Usage
**Created:** [April 3, 2020, 4:09pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975 "2020-04-03T16:09:02Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@oschulz](https://discourse.julialang.org/u/oschulz)
#### Post date: [April 3, 2020, 4:09pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975/1 "2020-04-03T16:09:02Z")
Is there a way to activate a shared named environment via `$JULIA_PROJECT` or `julia --project`, without using the absolute path? So, an equivalent to `] activate --shared myenv`?
---
### Author:  [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [April 3, 2020, 7:20pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975/2 "2020-04-03T19:20:12Z")
No.
---
### Author:  [@oschulz](https://discourse.julialang.org/u/oschulz)
#### Post date: [April 3, 2020, 7:23pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975/3 "2020-04-03T19:23:56Z")
Thanks, I’ll post an issue.
---
### Author:  [@oschulz](https://discourse.julialang.org/u/oschulz)
#### Post date: [April 3, 2020, 7:29pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975/4 "2020-04-03T19:29:47Z")
Done [Allow for specifying shared named environments on Julia start · Issue #35354 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/issues/35354)
---
### Author:  [@oschulz](https://discourse.julialang.org/u/oschulz)
#### Post date: [April 3, 2020, 7:31pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975/5 "2020-04-03T19:31:16Z")
One used case I have for this is passing an environment when combining VSCode/Julia with VSCode remote sessions (absolute path is different depending on remote system).
---
### Author:  [@oschulz](https://discourse.julialang.org/u/oschulz)
#### Post date: [April 3, 2020, 7:33pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975/6 "2020-04-03T19:33:13Z")
cc @davidanthoff
---
### Author:  [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [April 3, 2020, 7:43pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975/7 "2020-04-03T19:43:58Z")
Just FYI, you can do it with `JULIA_LOAD_PATH`.
---
### Author:  [@oschulz](https://discourse.julialang.org/u/oschulz)
#### Post date: [April 3, 2020, 7:48pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975/8 "2020-04-03T19:48:47Z")
True, though `$JULIA_LOAD_PATH` may already be set to system-dependent values, so fiddling with that to change the project is not always ideal and requires more care than `$JULIA_LOAD_PATH`. Also, it’s hard to pass env-variables via SSH (e.g. when starting remote processes) adding `--project=...` to the `julia` command is often easier.
---
### Author:  [@oschulz](https://discourse.julialang.org/u/oschulz)
#### Post date: [April 3, 2020, 7:50pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975/9 "2020-04-03T19:50:41Z")
Thanks for reminding me, though! I probably can use “$JULIA\_LOAD\_PATH” as a workaround in a specific use case I have for now.
---
### Author:  [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)
#### Post date: [April 3, 2020, 8:26pm UTC](https://discourse.julialang.org/t/activating-a-shared-named-environment-via-julia-project/36975/10 "2020-04-03T20:26:38Z")
@oschulz ah, that is an interesting point!