PROHOSTIVA
Documentation menuDeploy from a ZIP
Deploy

Deploying from a ZIP

No Git and no command line: upload your project as a ZIP and ProHostiva works out how to build and run it.

Prepare the ZIP

Any supported project can be deployed from a ZIP: a plain HTML site, a React or Vue app, a Next.js, Python, PHP or Rails app. See Supported frameworks.

  1. Find your project folder

    It's the folder with files such as index.html, package.json, requirements.txt or composer.json directly inside it.

  2. Leave out what we install ourselves

    Delete (or don't include) node_modules, .venv, vendor, build output such as dist, and the .git folder. We install dependencies and build your project during every deployment, and these folders make the ZIP much bigger.

  3. Compress it

    On a Mac, right-click the folder and choose Compress. On Windows, right-click it and choose Send to → Compressed (zipped) folder. Zipping the folder itself is fine: if everything is inside one top folder, we look inside it.

Keep secrets out of the ZIP

Don't include a .env file with real passwords or API keys. Add them in the dashboard as environment variables instead (see step 4 below).

Upload and deploy

  1. Upload the ZIP

    In your dashboard, click Host a website, choose Upload a ZIP and pick your file.

  2. Check what we found

    ProHostiva builds your project in a sandbox and shows whether it's ready, with anything to fix. You can carry on without waiting for it.

  3. Publish

    Name the website, choose its address and click Publish website. To put a new version online later, use Upload a new version in the Publish panel on the website's page.

  4. Add environment variables, if your project needs them

    API keys, database addresses and similar settings go in Developer settings → Environment variables. Tick Secret for anything private.

  5. Publish

    Click Publish. The deployment log shows each step: detecting, building, starting and checking your app. When it says Deployment successful, click Open website.

Updating your site

Make your changes, create a new ZIP, and upload it the same way. The new version replaces the old one only once it has built and started successfully; until then, and if anything fails, visitors keep seeing the current version.

Changing your site often? Deploying from GitHub saves you the zipping: push your changes and click Publish.

Limits

  • The ZIP can be up to 50 MB.
  • Unpacked, it can hold up to 5,000 files and 200 MB.
  • Symbolic links and files with unusual paths are refused, for the safety of every site on the platform.
For developers

The ZIP is unpacked in an isolated workspace, and the project must be at its top level (or inside one single top folder). Detection only reads files; nothing from your project runs until the build, which happens in an isolated container.