Table of Contents
Introduction
Modern web-application development heavily relies on frameworks. These sets of readily-prepared libraries make the actual programming a lot easier than it would be, unlike in ye older days. They provide tools varying from authentication to encryption, cookie and session handling to file uploads.
Despite the popularity of the PHP programming language and its many excellent frameworks, there are still time consuming challenges which take the developers away from the fun bits of creating the web-site (or API) they dream of.
In this the cloud provider article, following on our Capistrano Automation Tool Series, we will see how to introduce another little framework (or tool), this time to help you with pushing your code to your servers without dealing with SFTP file managers — *automatically!*
Glossary
1. Capistrano In Brief
2. Getting The Ruby Interpreter And Capistrano
- The Ruby Interpreter
- Capistrano
3. Preparing The Deployment Server
- Creating The Deployment User And Group
- Creating The Application Deployment Directory
- Setting Up PHP And Nginx
4. Preparing PHP Applications For Automated Deployments
- Initiating Git
- Initiating Capistrano
- Configuring Capistrano Deployment
- Configuring Production With Capistrano
- Deploying To The Production Server
5. Troubleshooting
Note: Although we will see how to download and set up the necessary dependencies for Capistrano (e.g. Ruby 2.1.0) to automate the deployment process, this article assumes that you already have your *deployment* droplet ready with a functioning web-site installation, online on an Ubuntu 13 cloud server.
Capistrano In Brief
—
Capistrano is a Ruby programming language based, open-source server (or deployment) management tool. Using Capistrano, arbitrary functions and procedures can be performed on virtual servers without direct interference by having Capistrano execute a script (i.e. a recipe) with all the instructions listed. In a general sense, this tool can be considered a developer's very own deployment assistant, helping with almost anything from getting the code on the remote machine to bootstrapping the entire getting-online process.
Originally written to help with Rails framework deployments, with its latest version, Capistrano 3 can now be used with (and for) almost anything, including PHP.
Note: If you would like to learn more about Capistrano and Ruby, check out our article on the subject: How To Use Capistrano to Automate Deployments: Getting Started.
Getting The Ruby Interpreter And Capistrano
—
The Ruby Interpreter
—
On your PHP development machine, you need to have the latest available Ruby interpreter in order to run Capistrano. The instructions below, explaining how to get Ruby on an Ubuntu VPS, is actually a quick summary of our detailed tutorial: Preparing An Ubuntu 13 Server To Run Ruby 2.1.0.
aptitude update
aptitude -y upgrade
aptitude install -y build-essential
aptitude install -y cvs subversion git-core libyaml-dev mercurial
curl -L get.rvm.io | bash -s stable
source /etc/profile.d/rvm.sh
rvm reload
rvm install 2.1.0
Capistrano
—
Once Ruby is installed, Capistrano can be set up using the default Ruby package manager RubyGems.
Run the following command to download and install Capistrano 3 using gem:
gem install capistrano –no-ri –no-rdoc
Preparing The Deployment Server
—
As a mature automation tool, Capistrano is built with stability and security in mind. In order to use it to deploy your PHP web applications, we first need to perform some work on the deployment server, e.g. create a user-group for Capistrano to use to connect to it.
Creating The Deployment User And Group
—
Add a new user group:
sudo addgroup www
Create a new user and add it to this group:
sudo adduser deployer
sudo adduser deployer www
Edit /etc/sudoers using the text editor nano to let the user deployer sudo for future deployments:
nano /etc/sudoers
Scroll down the file and find where root is defined:
..
root ALL=(ALL:ALL) ALL
..
Append the following right after root ALL=(ALL) ALL:
deployer ALL=(ALL:ALL) ALL
This section of the /etc/sudoers file should now look like this:
..
root ALL=(ALL:ALL) ALL
deployer ALL=(ALL:ALL) ALL
..
Press CTRL+X and confirm with Y to save and exit.
Note: To learn more about SSH and sudo, check out the cloud provider community articles on Linux Basics.
Creating The Application Deployment Directory
—
On the deployment server, we also need to define and create the directory where the PHP codebase will be located for the web-server to run the application.
Create the www web-application directory inside /var:
sudo mkdir /var/www
And set the permissions to make it access for the web-server (i.e. Nginx):
sudo chown -R :www /var/www
sudo chmod -R g+rwX /var/www
sudo chmod g+s /var/www
Setting Up PHP And Nginx
—
Capistrano's duty is to automate deployments. We still need to set up PHP and NGinx – or any other web-server & interpreter combination – to get our web-application working.
In order to fully prepare the deployment server to run PHP web-applications, check out the following articles:
- Nginx, PHP and MySQL:
- phpMyAdmin:
Preparing PHP Applications For Automated Deployments
—
Once we are done installing Ruby and Capistrano on our development server, and adding a deployment user on the deployment machine, we can see how to "initiate" Capistrano to get started with the tool.
Note: In this section, we assume that your web-application source code is located at /home/developer1/my_app directory. The following commands need to be executed *from within*.
cd /home/developer1/my_app
Initiating Git
—
Git is a source-code management system and revisiting tool commonly used by developers. Capistrano controls and manages your application lifecycle and deployment process through Git repositories.
In this section, we will create a centrally-accessible Git repository, initiate Git and upload your project there for Capistrano to use during deployments.
Note: In order to follow this section, you will need a Github account and an empty repository created.
Execute the following, self-explanatory commands inside the directory where your application's source code is located (e.g. my_app) to initiate a repository:
git init
git add .
git commit -m "first commit"
git remote add origin [email protected]:user123/my_app.git
ssh-keygen -t rsa
cat /root/.ssh/id_rsa.pub
git config –global user.name "user123"
git config –global user.email "[email protected]"
git push -u origin master
Note: To learn more about working with Git, check out the How To Use Git Effectively tutorial at the cloud provider community pages.
Initiating Capistrano
—
In this step, we will get Capistrano to automatically scaffold its configuration and deployment files inside the project directory.
Run the following to initiate (i.e. *install*) Capistrano files:
cap install
Configuring Capistrano Deployment
—
The file config/deploy.rb contains arguments and settings relevant to the deployment server(s). Here, we will tell Capistrano to which server(s) we would like to connect and deploy.
Run the following to edit the file using nano text editor:
nano config/deploy.rb
Add the below block of code, modifying it to suit your own settings:
set :application, 'my_app'
set :scm, :git
set :repo_url, 'https://github.com/user123/my_app.git'
set :deploy_to, "/var/www/my_app"
set :pty, true
set :format, :pretty
Press CTRL+X and confirm with Y to save and exit.
Configuring Production With Capistrano
—
Note: Similar to config/deploy.rb, you will need to make some amendments to the config/production.rb file. You are better modifying the code instead of appending the below block.
Run the following to edit the file using nano text editor:
nano config/deploy/production.rb
Enter your server's settings, similar to below:
role :app, %w{[email protected]}
server '162.243.74.190', user: 'deployer', roles: %w{app}
set :ssh_options, {
forward_agent: false,
auth_methods: %w(password),
password: 'user_deployers_password',
user: 'deployer',
}
Press CTRL+X and confirm with Y to save and exit.
Deploying To The Production Server
—
Once we are done with the settings, it is time to deploy.
Run the following code on your development machine to deploy to the production server. As defined in the above files, Capistrano will:
- Connect to the deployment server
- Download the application source
- Perform the deployment actions
Once all settings are done, you can run the following command to get Capistrano deploy your application source from your development server to deployment machine:
cap production deploy
And that's it! Now, you can watch Capistrano take your code online and keep track of your most recent code base.
Troubleshooting
—
Working with Capistrano is not always as straightforward as it might seem. Unfortunately, the tool likes to complain instead of guiding and the documentation, at its current stage, is a little bit limited.
For everything to work smoothly, try to:
- Match the directory and the repository names.
- Type everything correctly.
- Make sure that your development and deployment servers contain all necessary tools (i.e. sqlite3, libraries etc.).
- Make sure to test all operations and executions manually before getting Capistrano perform them.
- Consider implementing a more secure authentication method following the official Capistrano docs.
To learn more about Capistrano and what it can do, consider reading the [Capistrano documentation](capistranorb.com/documentation).
href="https://twitter.com/ostezer">O.S. Tezer</a></div>
