# Nice workflows for using and developing in Julia 1.9+

**URL:** <https://discourse.julialang.org/t/nice-workflows-for-using-and-developing-in-julia-1-9/96017>\
**Category:** General Usage\
**Tags:** tutorials\
**Created:** [March 13, 2023, 5:48pm UTC](https://discourse.julialang.org/t/nice-workflows-for-using-and-developing-in-julia-1-9/96017 "2023-03-13T17:48:17Z")\
**Posts on this page:** 4\
**Page:** 3

<div class="post-metadata">

**Author:** ![fkjogu](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fkjogu/32/2416_2.png) [@fkjogu](https://discourse.julialang.org/u/fkjogu)\
**Post date:** [May 14, 2023, 5:50am UTC](https://discourse.julialang.org/t/nice-workflows-for-using-and-developing-in-julia-1-9/96017/41 "2023-05-14T05:50:15Z")

</div>

I tend to put the primary environment just into the Project folder (`aftivate .`). This way, I always know which primary environment I have associated with the project without the need to remember the path.  
It’s also easy to get rid of the project including the environment by just deleting the project folder.

I use a global (standard) environment for utilities.

Is there some benefit to aggregate all project environments in a common directory? I gather, it is easy to create and forget an environment when not having them in the project directory directly.

---

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [May 14, 2023, 9:40am UTC](https://discourse.julialang.org/t/nice-workflows-for-using-and-developing-in-julia-1-9/96017/42 "2023-05-14T09:40:43Z")

</div>

> [@fkjogu](#):
>
> Is there some benefit to aggregate all project environments in a common directory?

The reason to have a shared environment is to perform similar analysis of different data sets, without having to setup a new environment for each analysis.

In many other situations having the environment in the current folder is more appropriate.

---

<div class="post-metadata">

**Author:** ![cdawg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cdawg/32/9811_2.png) [@cdawg](https://discourse.julialang.org/u/cdawg)\
**Post date:** [May 29, 2023, 8:52am UTC](https://discourse.julialang.org/t/nice-workflows-for-using-and-developing-in-julia-1-9/96017/43 "2023-05-29T08:52:12Z")

</div>

This is a great help! I feel like I have some meaningful Julia environment understanding! I find myself using `@ __DIR__ ` for multiplexing environments, heading scripts with

```julia
import Pkg; Pkg.activate("$(@ __DIR__ )"*"/..")

```

I like the environments to be 1-1 with the folder or parent folder the script is in.

Wow 1.9 is really great. I know it was a hard one but the “feel” is so much better! 😍

---

<div class="post-metadata">

**Author:** ![GunnarFarneback](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gunnarfarneback/32/1827_2.png) [@GunnarFarneback](https://discourse.julialang.org/u/GunnarFarneback)\
**Post date:** [May 29, 2023, 9:04am UTC](https://discourse.julialang.org/t/nice-workflows-for-using-and-developing-in-julia-1-9/96017/44 "2023-05-29T09:04:51Z")

</div>

> [@cdawg](#):
>
> ```julia
> import Pkg; Pkg.activate("$(@ __DIR__ )"*"/..")
> 
> ```

A little nitpick: `"$(@ __DIR__ )"` is just a more complicated way to write `@ __DIR__ `. Also I would write the whole construction as `Pkg.activate(dirname(@ __DIR__ ))`.

[Previous page](https://discourse.julialang.org/t/nice-workflows-for-using-and-developing-in-julia-1-9/96017.md?page=2)