If your site or app lives in a git repository, you can deploy it straight from that repo instead of dragging files around. Flashcloud pulls from the repository you connect and places the code on your hosting.
Set up Git deployment
Git deployment is a tile in the portal:
- Go to Services → click your hosting → the Git tile.
- Connect a repository. We support GitHub, GitLab, Bitbucket, and any git server you can reach over SSH.
- Configure the deploy path and the branch to track.
- Push to the configured branch. We pull and deploy automatically.
This suits developers who treat the site as code: the source of truth is git, and the live site is a deployment artifact. It also fits CI/CD pipelines that push on merge.
Where your files land
For your main website, code belongs in public_html/. Set the deploy path accordingly so the pulled files end up where the web server serves from. A subdomain or addon domain has its own document root, so point its deployment at that folder instead.
Static output (HTML, CSS, JS) is served directly by LiteSpeed with no PHP or Node overhead, which makes Git deployment a clean fit for static site generators like Hugo, Astro, and Eleventy.
Apps that need a build
Many projects commit source, not the finished build. If your repo needs a build step (for example, compiling assets or running a bundler) before the site is servable, make sure the built output is what lands in your document root. The safest pattern is to build in your pipeline and either commit the build output or deploy the already-built files.
Other ways to get code onto the server
Git is one of three upload paths. If a repo is not the right fit for a given job, you can also use the portal file manager or an FTP/SFTP client. See Uploading files to your hosting for all three, and FTP and SFTP accounts for connection details and scoped accounts.
For automated deploys over SSH, prefer key-based authentication over a password. Generate a keypair, add the public key to your account's SSH key settings, and connect with the private key so no credentials sit in your CI logs.
If a deploy does not appear
- Files pulled but the site does not update: check the deploy path points at
public_html/(or the correct subdirectory), not the home directory. - Push does not trigger a deploy: confirm you pushed to the exact branch configured in the Git tile.
- Permission errors: see File permissions.