What to include in a project ZIP before deployment
Make a clean project archive with the code and build files, without dependencies, secrets or local clutter.
App Cities · 2 min · Updated
Your project folder may contain much more than your app needs. Large dependency folders slow down uploads. Secret files can expose private access. A clean ZIP contains the files needed to build and run your app, not a copy of your whole computer.
The steps
- Include source code, dependency files and lockfiles. Add Dockerfile and Compose files when your project uses them.
- Leave out node_modules, .git, old builds and local caches. The builder should install the right dependencies from your project files.
- Remove .env files and private keys. Write down the names of required variables, then enter their values through the secret-entry page.
- Check the folder layout. Build paths must still point to the correct files after the archive is unpacked.
A common question
Can I upload a folder instead?
The dashboard supports a folder upload flow. The same rules apply: send the needed project files, not local secrets or installed dependencies.
Ready to try your project?
Prepare your project, check the prices and choose how you want to deploy.