Laravel Forge deployment hook
Laravel Forge
Add two small curl calls around the deploy command you already use. Forge runs them on the server, DeployState turns them into one clear desktop signal.
Set up Laravel ForgeIntegration guides
Your deploy tool already knows what to say.
DeployState works with ordinary HTTP calls. Pick the platform that runs your deployment, keep the private hook URL in its secret store, and send the lifecycle signals around work already in place.
Choose your deployment platform
Five practical ways to get the first signal.
Laravel Cloud deployment hook
Laravel Cloud
Keep deployment state next to your Laravel Cloud release. A private DeployState hook starts before the release work and closes when the deployment hook succeeds.
Set up Laravel CloudGitHub Actions workflow
GitHub Actions
Store the private hook URL in GitHub Actions secrets, then send a start event before deploy and a completion or failure event after it settles.
Set up GitHub ActionsDeployer PHP recipe
Deployer
Use Deployer’s lifecycle events to publish a start signal, then resolve the same DeployState step when the deployment is successful or fails.
Set up DeployerPloi deployment script
Ploi
Ploi already runs the commands that matter. Add a private DeployState hook before and after those commands to make the state visible everywhere your team needs it.
Set up PloiPrivate by default
The full hook URL is the credential.
Every sequence step has a unique private URL. Save it as an encrypted deployment secret, never commit it to a repository, and rotate it from the step editor whenever you need to.