# Understanding the startup.jl file -- is there a environment-specific version?

**URL:** <https://discourse.julialang.org/t/understanding-the-startup-jl-file-is-there-a-environment-specific-version/77998>\
**Category:** New to Julia\
**Tags:** question, startup\
**Created:** [March 16, 2022, 10:47pm UTC](https://discourse.julialang.org/t/understanding-the-startup-jl-file-is-there-a-environment-specific-version/77998 "2022-03-16T22:47:28Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![c42f](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/c42f/32/52842_2.png) [@c42f](https://discourse.julialang.org/u/c42f)\
**Post date:** [March 17, 2022, 2:25am UTC](https://discourse.julialang.org/t/understanding-the-startup-jl-file-is-there-a-environment-specific-version/77998/2 "2022-03-17T02:25:55Z")

</div>

I don’t know about a builtin way to do this. But you could add the following in your global startup.jl:

```julia
let
    local_startup = joinpath(dirname(Base.active_project()), "startup.jl")
    if isfile(local_startup)
        include(local_startup)
    end
end

```

> [@Jason\_Mercer](#):
>
> users may not be able to edit the startup.jl file

If you had this problem, you can set the environment variable `JULIA_DEPOT_PATH` to modify where your Julia packages are installed and where your global `startup.jl` is read from.

---

_[View the full topic](https://discourse.julialang.org/t/understanding-the-startup-jl-file-is-there-a-environment-specific-version/77998)._