Deploying from GitHub

1. Start a new website

   In your dashboard, click Host a website and choose GitHub repository. (For a website you already have, use Change source in its Publish panel.)

2. Click Connect GitHub

   GitHub asks which account to use and to authorise ProHostiva; after you approve, you're brought back to the same step.

1. Pick the repository

   Your repositories are listed, most recently updated first; search to find one. Click it, and change the branch if you don't deploy from the default one (usually main).

2. Let us check it

   We build it in a sandbox and show whether it's ready, with anything to fix. Only you can see this report, even for a public repository.

3. Add environment variables (if needed)

   API keys and other settings go in Developer settings → Environment variables, not in the repository.

4. Publish

   Name the website and click Publish website. We download the latest commit, build it in an isolated container, check that it answers and put it live. After you push changes, click Publish latest version in the Publish panel on the website's page.

Push your changes to GitHub as usual, then click Publish latest version on the website's page. Deployments are one click, not automatic on every push, so nothing goes live until you decide.

• Connecting GitHub lets ProHostiva list your repositories (public and private) and download the one you choose when you deploy. Private repositories work the same way as public ones.
• Your GitHub access token is stored encrypted. It's only used to list your repositories and download the one you picked; ProHostiva never writes to them.
• You can disconnect a repository from a website at any time, and revoke ProHostiva's access in your GitHub settings under Applications.

• "Couldn't load your GitHub repositories": GitHub may have revoked the access (for example after you changed your password). Click Reconnect GitHub.
• Your app is in a subfolder of the repository (a monorepo): ProHostiva builds from the top level. Move the app to the root, or put it in a repository of its own.
• The build fails: see Troubleshooting.