// Knowledge base
Staging and GitHub deploy
Staging copies files only. GitHub deploys from a connected repository.
When the plan allows staging, the client portal can create or refresh a copy of the site at staging.example.com. Promoting staging copies those files onto the production site. The database is not copied in either direction. If the application stores content in the database, update that separately.
GitHub deploy uses a GitHub App connected under Admin, System, Integrations (or the reseller's own GitHub App). In the client portal, pick the repository, the branch and the target: production or staging. You can set a build command and an output directory. A push to that branch can deploy on its own. You can list file patterns to leave untouched, and a command to run after deploy.
The build runs in a sandbox and does not receive the panel's secrets. Do not put production passwords in the repository.