
Tutorialby
A clean
archive.
Without your secrets, without touching the project.
Handing us your project as an archive rather than through GitHub? Two things must never travel with it. Everything happens on a copy: your project itself stays untouched. Count two minutes.
Duplicate, clean the copy, compress: the archive that passes the intake check the first time.
Five steps.
- 01
Right click on your project folder, Duplicate (copy and paste on Windows). Everything that follows happens in the copy.
- 02
In the copy, delete node_modules, the warehouse of downloaded parts: heavy, and it rebuilds itself.
- 03
Delete the .env file from the copy: it holds your real passwords. Keep a .env.example with the same names, without the values.
- 04
Right click on the copy, Compress (Send to, Compressed folder on Windows). The zip appears next to it.
- 05
Drop that zip into your space, up to two gigabytes. The copy can go to the trash, your project has not moved.
Word for word.
What the video says, to read at your own pace or find one word again.
Read the full transcript
Handing us your project as an archive? Two things must never travel with it. We do not touch your real project: we clean a copy.
Right click, Duplicate. Everything we do now happens in the copy: your project itself does not move.
First, node_modules. That folder is the warehouse of downloaded parts: heavy, and it rebuilds itself, on your machine as on ours. To the trash.
Then the .env file: it holds your real passwords. It never goes into the archive, and the original stays untouched in your project. In its place, a .env.example: the same names, without the values. We know what to plug in, without ever seeing your secrets.
Right click on the copy, Compress. This zip file is what you drop into your space, up to two gigabytes. The copy can go to the trash afterwards, your project has not moved.
On arrival, your archive is read, never executed. If a password or real data is still lying around, the audit waits and we tell you: nothing goes forward until it is clean.
The other tutorials
Get your project audited
Your code is online and we have read access. We look for what breaks and what leaks, then hand you the list of what to fix, in order.
See the audit serviceWe refuse your passwords: the code only, never your credentials.

