# Is startup.jl an acceptable place to store credentials for interactive scripts?

**URL:** <https://discourse.julialang.org/t/is-startup-jl-an-acceptable-place-to-store-credentials-for-interactive-scripts/98343>\
**Category:** General Usage\
**Tags:** security\
**Created:** [May 4, 2023, 8:39pm UTC](https://discourse.julialang.org/t/is-startup-jl-an-acceptable-place-to-store-credentials-for-interactive-scripts/98343 "2023-05-04T20:39:10Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![mkjohnson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkjohnson/32/211111_2.png) [@mkjohnson](https://discourse.julialang.org/u/mkjohnson)\
**Post date:** [May 4, 2023, 9:26pm UTC](https://discourse.julialang.org/t/is-startup-jl-an-acceptable-place-to-store-credentials-for-interactive-scripts/98343/4 "2023-05-04T21:26:28Z")

</div>

I looked into `DotEnv.jl`, I think I avoided it because the package hasn’t been updated in so long I thought maybe it had been abandoned/wasn’t supported anymore 😅

Is the persistence across projects the only downside in your view? In the very specific use-case I’m thinking of that sparked this question (an internal analytics package), a limited set of variables shared amongst all projects is not necessarily a bad thing! For example, if you’re only using one database for all your projects then it makes sense for those credentials to be accessible across projects.

But I can see how this could get messy if credentials were highly project-specific. In which case `.env` files would definitely be the best way to go as far as I can tell.

---

_[View the full topic](https://discourse.julialang.org/t/is-startup-jl-an-acceptable-place-to-store-credentials-for-interactive-scripts/98343)._