3. Build and zip your site
MultiConnectCloud serves what you upload. It does not install packages or run your build, so build locally or in CI first, then zip the output folder, not your source code.
The zip layout
The simplest layout zips the contents of the output folder, so index.html is at the top of the zip.
Script 3.1: build.zip after a Vite build, zipping the contents of dist
build.zip
├── index.html ← at the top level
├── favicon.ico
└── assets/
├── index-3f9a1c.js
└── index-8b2e4d.css
You can also zip a folder that contains the output folder, such as your whole project after a build. Then index.html is one level down, and the output folder is found for you, as described below.
Script 3.2: build.zip with the output folder inside it
build.zip
└── dist/
├── index.html
└── assets/
└── index-3f9a1c.js
Making the zip
Script 3.3: build and zip on macOS or Linux
npm run build
cd dist && zip -r ../build.zip .
Script 3.4: build and zip on Windows (PowerShell)
npm run build
Compress-Archive -Path dist\* -DestinationPath build.zip
Replace dist with your framework's folder from Section 2. The upload must be a real .zip file, and its size limit comes from your hosting plan: the form shows it as Max Upload Size.
How the output folder is found
When the build is uploaded, MultiConnectCloud looks inside the zip for index.html:
| Build Output Directory | What happens |
|---|---|
| Blank | The folder with the index.html nearest the top of the zip is served. For Script 3.1 that is the top of the zip; for Script 3.2 it is dist |
Set, and that folder has an index.html |
That folder is served |
Set, and that folder has no index.html |
The deploy is refused, and the message lists the folders where index.html was found |
Any value, and the zip has no index.html at all |
The deploy is refused. You probably zipped your source, not your build |
Leaving it blank is the right choice for most sites. The folder that was used is shown on the website page as Resolved Build Output Directory.
When you upload a new build without changing Build Output Directory, the folder from the last build is treated as a hint: if the new build has no index.html there, the folder is found again, as if the field were blank. A folder you change is always held to, and the deploy is refused if it is wrong.

