Servers

What servers do

Servers are the runtime home for sites, databases, PHP services, SSH access, commands, scheduled jobs, queue workers, and maintenance actions. The server workspace separates initial provisioning from ongoing operations so the team can see what happened and what still needs attention.

Before provisioning

• Choose a connected cloud provider with fresh metadata.
• Pick the project, region, image, size, hostname, and SSH key.
• Decide which runtime services are required, such as PHP, database, Redis, Supervisor, and firewall defaults.
• Confirm whether production sites will share a server or need isolated infrastructure.

Typical workflow

1. Connect and sync the infrastructure provider.
2. Create a server from the dashboard.
3. Follow provisioning progress until the server reaches a ready state.
4. Review runtime status, public IP, installed services, and activity history.
5. Attach sites, databases, keys, schedulers, processes, and maintenance tasks as needed.

Checks before attaching sites

• Provisioning completed without a failed required step.
• The server has a reachable public IP.
• Required PHP and database services are installed.
• SSH access is understood and limited to the right people.
• Backup and recovery expectations are documented for production use.

Common issues

• A selected region or size disappears because provider metadata is stale.
• Runtime packages are missing because the server was created with the wrong options.
• A maintenance task is queued while another server action is still running.
• Team members inspect the cloud provider directly and miss the ForgedBase activity trail.

Related guides

• How to deploy a Laravel site on a cloud server
• How to choose a cloud provider for agency sites
• How to plan server backups and recovery for agency sites