Git repository deployment

Webcore can associate a managed site with a Git repository and deploy repository content into the site's document tree. This is intended for controlled application, theme and other code deployments without manually copying files onto the hosting node.

Repository settings

A Git deployment has four important settings:

• Repository URL — the Git repository to fetch.
• Branch — the branch Webcore tracks and deploys.
• Repository path — an optional subdirectory inside the repository to deploy.
• Deployment path — the destination inside the managed site's document root.

Repository path and deployment path are deliberately separate. For example, a repository can contain an entire project while Webcore deploys only theme/webcore to wp-content/themes/webcore.

Deploy keys

Webcore provides a site-specific public SSH key for repositories that use SSH authentication. Add the displayed public key to the repository as a deploy key with only the permissions required to fetch the repository.

The hosting node keeps the corresponding private credential outside the public site files.

Adopting an existing deployment

If the deployment target already exists, Webcore does not blindly overwrite it. Adoption verifies that the existing target matches the selected repository content before Git management is established.

Remove temporary files or other local differences before adopting an existing directory. This protects a live site from being silently replaced by repository content that does not match it.

Deployment behaviour

Deployments are manually triggered from the Panel. Webcore fetches the configured branch and permits a deployment only when it can move forward safely from the currently deployed revision.

For repository-subdirectory deployments, Webcore prepares the selected subtree outside the public target and atomically replaces the deployment directory. The live target does not contain the repository's .git metadata.

Existing deployment-directory permissions are preserved during replacement. For a new deployment target, Webcore uses a web-readable directory mode while retaining Git-controlled modes inside the deployed tree.

Safe workflow

1. Configure the repository URL and branch.
2. Set Repository path if only part of the repository should be deployed.
3. Set the destination Deployment path.
4. Add the displayed deploy key to the repository when SSH authentication is used.
5. Fetch/status-check the repository.
6. Adopt an existing target only after the Panel reports an exact match.
7. Deploy the new revision from the Panel.
8. Validate the site after deployment.

Current deployment model

Git deployment is intentionally explicit: deployment is initiated from the Panel rather than automatically from repository webhooks. This keeps the production change visible and controlled while the deployment workflow evolves.