After a long road through alpha, beta, and release candidates, Deployer v8 is finally out. This release modernizes the foundations of Deployer, introduces a new recipe format, and tightens up many of the rough edges that accumulated over the v7 cycle.
Deployer v8 introduces MAML-based recipes as a replacement for YAML, while PHP recipes remain unchanged. This shift raises an important question: why move from YAML to MAML? In this blog post, I will explain the rationale behind this decision.
{
import: ["recipe/common.php"]
hosts: {
"deployer.org": {
remote_user: "deployer"
deploy_path: "~/deployer.org"
}
}
tasks: {
deploy: [
"deploy:prepare"
"deploy:publish"
]
build: [
{ runLocally: "npm run clear" }
{ runLocally: "npm run build" }
]
"deploy:update_code": [
{
upload: {
src: "build/"
dest: "{{release_path}}"
}
}
]
}
}
We're excited to announce the release of the Official Deployer Docker Image! This image simplifies the deployment process for anyone using Deployer, providing a pre-configured environment ready to handle your deployment tasks right out of the box.
It’s hard to believe that Deployer has been around for a decade. What started as a small tool—born out of frustration with setting up Ruby for deployment—has now grown into one of the de facto standards for deploying PHP applications. Today, millions of websites rely on Deployer, and over the past ten years, we’ve powered more than a 1 000 000 000 deployments.
As we look to the future, we’re excited about what’s coming. We’ve got a host of new features in the pipeline, all designed to make your deployment process even smoother and more efficient. And after ten years, it’s also the perfect time to refresh our look. Here it is, fresh for the next chapter of Deployer.