Why do we need it?¶
As we wanted the end-user to be able to work from everywhere into the filesystem,
we created a logic which will create and keep the
output/ directory which complies
with our code.
How does it work?¶
Want to read the code ? It’s here
After each version, the maintainer does a
--production which will prepare the repository
That has the side effect to map the maintainer version of the
directory into a file called
Once pushed, on the end-user side, when testing for file, that file is downloaded into
a file called
dir_structure.json which is then used to restore/create a
a perfect copy of the output directory the maintainer had when pushing the new
If you find yourself in a case that a directory is not found, please try first to
dir_structure*.json files to force a resynchronization.
How to generate it manually?¶
You can’t. But using the
--dir-structure argument will do the job on purpose.