Automation
Deployer automates the deployment process, which reduces the potential for human error and saves time compared to manual deployments.
Ease of Use
Designed with simplicity in mind, Deployer leverages PHP, making it accessible for developers familiar with the language, and provides a clear syntax for setting up deployments.
Customizability
Users can customize their deployment process through hooks and tasks, allowing Deployer to suit a wide range of use cases and project types.
Rollback Support
Deployer offers easy rollback capabilities, which can revert deployments to a previous stable state, providing a safety net in case something goes wrong.
Active Community
An active user community and regular updates ensure that Deployer stays current, secure, and compatible with other tools.
Yes, Deployer is generally considered a good tool for PHP application deployment. It is particularly valued for its ease of use and powerful features that cater to various deployment needs.
We have collected here some useful links to help you find out if Deployer is good.
Check the traffic stats of Deployer on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of Deployer on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of Deployer's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of Deployer on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about Deployer on Reddit. This can help you find out how popualr the product is and what people think about it.
This post walks through how to build an Ansible repo to manage a production DigitalOcean setup: two Ubuntu droplets, six Laravel apps, a couple of PHP framework sites, and a Go microservices platform. The goal is to codify everything that was previously managed via manual SSH, without replacing the Deployer workflow that already handles app releases. - Source: dev.to / 4 months ago
Still use php deployer each day and works with symlinks as well. https://deployer.org/. - Source: Hacker News / 6 months ago
Deployer offers PHP developers a streamlined, zero-downtime deployment process, supporting major PHP frameworks. It is the ideal choice for secure, interruption-free deployment, automating and simplifying deployment tasks in the PHP environment. - Source: dev.to / over 2 years ago
I use deploybot.com to handle like 10 different Drupal installs, on a shared hosting. See also https://deployer.org but you can have your "light" platform.sh on a reasonably cheap shared hosting. Source: about 3 years ago
Yes, in combination with PHP deployer: https://deployer.org/. Source: over 3 years ago
Is there an equivalent for deployer in .NET world? https://deployer.org/. - Source: Hacker News / over 3 years ago
We have recently moved from jenkins + deployer.org to envoyer.. Alot of value and ease of life considering the monthly fee.... Source: over 3 years ago
The easiest way to switch from your current ssh -> git pull deployment to CI deployment is the switch to Deployer. https://deployer.org/ which is doing something similar but in a blue/green deployment way. A github action for it can look like this:. Source: over 3 years ago
I would also check out PHP Deployer (https://deployer.org/) as an open source/free alternative to some of those paid solutions mentioned in other comments. Source: over 3 years ago
We run a GitHub Actions workflow on push to master / PR merges for our Laravel apps that builds our assets, runs tests & code quality checks, then deploys to our server(s) using Deployer. Source: over 3 years ago
I use deployer and deployphp github action. Source: over 3 years ago
Setup blue/green deployments or go fancy with something like deployer. Source: over 3 years ago
I'm not looking for a hosting, I'm looking for the equivalent of deployer.org for node. A package that handles the process to git pull, install dependencies, rollback if necessary, etc... When I search for "how to deploy a node app" all I get is tutorials on how to deploy to Heroku, Vercel & other cloud providers :(. Source: almost 4 years ago
If you aren't then https://deployer.org/ is pretty easy for beginners. Source: almost 4 years ago
Yes, like Deployer. Or I deliver my crap in a way that doesn't use git directly (if at all), like docker images that already include all of the code needed. Source: almost 4 years ago
The following Deployer workflow is a nice option if your target production server supports composer, NodeJS and SSH. You can write your deploy routine in PHP (instead of fiddling around with Github Action pipeline commands) and test it beforehand locally. - Source: dev.to / almost 4 years ago
Namespace Deployer; Require 'contrib/npm.php'; // https://deployer.org/docs/7.x/contrib/npm Import('recipe/statamic.php'); // https://deployer.org/docs/7.x/recipe/statamic Set('application', 'My Statamic Site'); // The git repository which should be used Set('repository', 'git@github.com:mandrasch/my-statamic-site.git'); // Targets for deployment (SSH), // this will be called via 'ddev dep deploy... - Source: dev.to / about 4 years ago
We also currently deploy using a script which ssh's in to the server (similar to Deployer) which needs access. Source: about 4 years ago
Two deployment techs I use for non-containerized apps work in roughly the same way. Capistrano And Deployer. Source: about 4 years ago
Second, as you are using this for deployment, I would properly recommend using tools designed for that, it could be deployer. Source: over 4 years ago
SSH-ing into servers and doing a git pull is an approach I've used before with PHP. One thing to lookout for is if that server is taking requests during the git pull. If so, this can lead to some requests failing as files change during the pull. A way to address this is to have a symlink'ed webroot. That way you can keep multiple copies of your repo on the server and swap the symlink once the git pull is done.... Source: over 4 years ago
Do you know an article comparing Deployer to other products?
Suggest a link to a post with product alternatives.
Is Deployer good? This is an informative page that will help you find out. Moreover, you can review and discuss Deployer here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.