How to deploy a PHP site with Git and SSL

Why simple PHP sites still need a launch workflow

Not every client site is Laravel or WordPress. A plain PHP site can still need a proper cloud server, Git deployment, domain checks, HTTPS, backups, and safe access. The workflow can be lighter, but it should not be casual.

ForgedBase gives small PHP projects the same operational visibility as larger applications without forcing unnecessary framework assumptions.

Prerequisites

• A PHP site in a Git repository.
• A supported provider account connected to ForgedBase.
• A domain or subdomain.
• Any required PHP version, extensions, or environment values.
• A backup and handoff expectation.

Step-by-step workflow

1. Connect and sync the cloud provider.
2. Create a server with the right PHP runtime needs.
3. Create the PHP site in ForgedBase.
4. Connect the source-control repository.
5. Review the deployment command.
6. Add the domain while DNS is still safe to change.
7. Point DNS to the server.
8. Issue SSL after DNS resolves correctly.
9. Run the first Git deployment.
10. Configure backups and team access.

Where ForgedBase helps

ForgedBase keeps the site launch from becoming a manual file-copy habit. The provider, server, repository, domain, SSL certificate, deployment history, and backup plan stay visible in one workspace.

That is useful for smaller sites because maintenance often happens months later, when the original launch details are easy to forget.

Common issues to check

• Files are edited manually on the server instead of deployed from Git.
• DNS is changed before the new site is ready.
• SSL is requested before DNS points correctly.
• The PHP version is different from the development environment.
• There is no backup plan because the site is considered small.
• Access keys are shared instead of reviewed.

Related ForgedBase docs

• Sites
• Deployments
• Domains and SSL
• Source-control deployment guide
• Domain and SSL guide
• Backup planning guide

PHP launch checklist

• Provider connected.
• Server ready.
• PHP runtime confirmed.
• Repository connected.
• Deployment command reviewed.
• Domain verified.
• SSL active.
• Backups configured.
• Access reviewed.