# Fully archive working environment (When Manifest is not enough)

**URL:** <https://discourse.julialang.org/t/fully-archive-working-environment-when-manifest-is-not-enough/118446>\
**Category:** General Usage\
**Tags:** question, reproducibility\
**Created:** [August 21, 2024, 9:21am UTC](https://discourse.julialang.org/t/fully-archive-working-environment-when-manifest-is-not-enough/118446 "2024-08-21T09:21:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![filchristou](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/filchristou/32/26760_2.png) [@filchristou](https://discourse.julialang.org/u/filchristou)\
**Post date:** [August 21, 2024, 9:21am UTC](https://discourse.julialang.org/t/fully-archive-working-environment-when-manifest-is-not-enough/118446/1 "2024-08-21T09:21:50Z")

</div>

Is there a way to take a working environment and fully archive it to be 100% reproducible offline ?

E.g., I have a messed-up project that consists of

- public registry packages
- unversioned github packages
- local packages

I would like to wrap everything (including the julia version) and ship it (no binaries but working code as usual).  
The recipient shouldn’t rely on internet connection but rather get all the code needed directly from the archive.  
I guess that gets complex because a partial instance of the `JULIA_DEPOT` needs to be copied and I am not aware of any discussions in this direction.