What is Reddit's opinion of Deployer?

From 3.5 billion Reddit comments

We use deployer.org. It's a bit like capistrano/capifony but written in PHP so the deployment configs/recipes are also written in PHP.

Your source is deployed to a new release directory and only once all tasks are successfully completed is the symlink to the "current" switched to the new folder. Release history is retained so rolling back is a single command.

I gave a short talk about it to the Thailand PHP User Group a few months back. Recently version 3.x was released which sees a number of improvements

The problem I see with stuff like this:

http://deployer.org/recipes/rsync

Is that you're effectively creating a new interface for the rsync command line tool. You're still stuck learning how rsync works, except you have an additional layer to deal with, while missing out on things like standard unix pipes.

If that's 'configuration' then so is writing a Makefile. And Make has the additional benefit that it doesn't require someone to create recipes for standard executables. It already works without it.

This is indeed the way to go, many deploy tools handle it this way.

It's worth it checking out these deploy tools:

• Deployer
• Rocketeer
• Capistrano

How about Rocketeer? Or Deployer?

Edit: I should read the whole post before commenting...

Edit again: I just mistook u/rmas comment, as your post... It's late, I should get off reddit

For personal projects, I've used http://deployer.org/. It's actually pretty neat and ties very well with PHP environments, since it is itself written in PHP.

Here's an example of my deployment configuration/code.

it basically ssh's into your server, creates a new directory, pulls from your repo, runs all your dependency managers, run your db migrations (well, it will soon), switches symlinks to point to new code, restarts nginx, and then removes old directories while keeping a few recent releases around in case you need to revert quickly. That's not much code in that file I pointed to for the amount of things I listed above. And I'm just using the vanilla deploy config. There's ones for symfony and laravel, etc.

We use:

• Forge for spinning up new servers
• Forge for deployment for really simple static sites (plain HTML or very simple PHP sites)
• deployer.org for apps (It's basically the same what envoyer does (simlinks single releases))

For us, the price is more than justified. Currently, we have like 30 active servers and managing them with Forge is really easy and convenient. I'm also currently activating Let's Encrypt Certificates on all sites and it's just SOOO easy with Forge ;)

I personally would recommend using git and optionally a deployment script to push changes without needing ftp. Then once you push a change you could either do a git pull on the server or use your deployment script which does all that for you. If you're working with legacy code on a huge code base then use ssh w/ something like WinSCP.

Fair enough, but just wanted to mention that, if PHP is your most comfortable programming environment, you can script things in php.

Just create a file:

touch myscript

Give it executable perms:

chmod a+x ./myscript

Add this to the top of your php file:

#!/usr/bin/env php <?php

And then now you have a command line script that is written in PHP.

(hope this doesn't come across patronizing)

Other than that, I highly recommend: http://deployer.org/

seems like after further research, a possible way is to

• run bin/magento setup:upgrade locally
• copy the extension files to production
• run bin/magento setup:upgrade on production

also ran across a cool tool at

http://deployer.org/

there's not a recipe for magento2 yet, so I will see if I can come up with one. If anyone else has one, that would be helpful.

If you are on a shoestring budget, you could no the following:

• Amazon has free t2.micro instances for new users. It is a really low end machine, but hey it's free.
• Use PuPHPet to configure your server. Just use the simple web interface to configure what you need and deploy directly to Digital Ocean, AWS etc.
• For deployment, you can use Deployer for free
• Skip buying your own domain and use some of the free dynamic DNS services like No-IP to get an alias atleast

The current "standard" is to set up a folder where version 1 of your code is deployed (deploy/1), then make your configured www dir a link to 1. When you have a new version, extract it to deploy/2, run any jobs that you need to run, then change the symlink to point to 2. The link change is technically not atomic but happens so fast that it's a negligible issue.

Check out deployer: http://deployer.org it can manage the whole process for you and also takes care of managing links to folders that are shared between deployments (like user uploads)

There are tons of different deployment options out there, but what about Envoyer? I have been using Deployer lately, it is free plus I can deploy to private VPS not open to outside world. Can be extended to do pretty much anything during the deployment.

Current work environment:

• Sourcetree / Git for SCM
• PHPStorm for IDE
• Vagrant for development environment
• Deployer.org for deployments
• PHPCI for CI (though seems development is dead so might be looking for something new)
• Asana / Trello for Project / Task management (trying to get rid of Asana)
• Slack for communication

Pretty happy with it apart from Project/Task Management. Slowly moving towards a scrum approach but it's taking a long time.

Also not looking forward to having to move to Jenkins if PHPCI development is truly dead (any other self hosted recommendations welcomed).