Sites

What sites do

Sites combine an application preset, server, repository or blueprint, runtime settings, environment values, domains, SSL, deployment settings, and activity history into one launch workspace. The goal is to keep the application and the operational work attached to the same place.

Before creating a site

• Pick the correct server and confirm it is ready.
• Choose the application preset, such as Laravel, WordPress, PHP, MyBB, or static HTML.
• Decide whether the site uses a custom repository, a branch or tag, a blueprint, or a manual upload path.
• Prepare the primary domain strategy and any temporary platform subdomain.

Typical workflow

1. Create the site from the dashboard.
2. Choose the application preset and source option.
3. Set the domain, document root, PHP version, database needs, and deployment behaviour.
4. Follow the site provisioning run.
5. Open the site workspace to manage deployments, domains, SSL, commands, notifications, and settings.

Checks before launch

• The site is attached to the intended server.
• The repository or blueprint source is correct.
• The document root and PHP version match the application.
• Environment values and database settings are present.
• The platform subdomain works before custom DNS is moved.

Common issues

• The site deploys, but the document root points to the wrong folder.
• The production branch is different from the branch the team expected.
• A domain is added before the site is reachable on its temporary hostname.
• Database credentials are created but not added to the application environment.

Related guides

• How to deploy a PHP site with Git and SSL
• How to deploy a WordPress site on DigitalOcean
• How to connect source control for site deployments