{"id":14508,"date":"2016-08-30T12:15:12","date_gmt":"2016-08-30T09:15:12","guid":{"rendered":"https:\/\/www.webcodegeeks.com\/?p=14508"},"modified":"2016-08-26T19:51:17","modified_gmt":"2016-08-26T16:51:17","slug":"getting-started-laravel-codeship-part-ii","status":"publish","type":"post","link":"https:\/\/www.webcodegeeks.com\/php\/getting-started-laravel-codeship-part-ii\/","title":{"rendered":"Getting Started With Laravel On Codeship – Part II"},"content":{"rendered":"

In the first part of this series<\/a>, I stepped through the basics of creating a continuous-deployment pipeline for a Laravel-based application using Codeship. We had a look at the application\u2019s overall structure, its configuration, created database migrations, and created some acceptance tests. We finished up by working through an initial Codeship project creation, so that the test-suite could be run whenever a push was made to the project\u2019s \u2248master branch in its GitHub repository.<\/p>\n

As I mentioned at the end of that article, it wasn\u2019t the whole story. We\u2019ve only gotten halfway down our continuous deployment pipeline. What\u2019s missing is the part where we actually deploy the application to a production (or testing or staging) server. That\u2019s what we\u2019re going to do in this, the second and final, part of the series.<\/p>\n

Specifically, we\u2019ll cover how to refactor the application, so that it uses a PostgreSQL database, instead of SQLite. I\u2019ll demonstrate how to update the environment configuration, so that it includes the relevant variables necessary to test the build, using Codeship\u2019s PostgreSQL database, available in all projects.<\/p>\n

We\u2019ll wrap things up by deploying the project to a DigitalOcean droplet. We\u2019ll also see how to use ElephantSQL as our host, instead of a PostgreSQL installation on the droplet.<\/p>\n

Let\u2019s get started.<\/p>\n

Updating the Environment Configuration<\/h2>\n

The first thing we need to do is update the environment configuration variables. Specifically, we need to change the database-related ones and then add some extra variables to support the deployment process.<\/p>\n

Did you know that every Codeship build contains an installation of PostgreSQL<\/a>? Codeship provides support for versions 9.2\u20139.5, as at the time of writing.<\/p>\n

Regardless of what version you need, it\u2019s easy to access. The port number you use has symmetry with the PostgreSQL version number. So, version 9.2 is available on port 5432, version 9.3 is available on port 5433, and so on.<\/p>\n

So the first thing we\u2019re going to do is change the DB_CONNECTION<\/code> environment variable to be pgsql<\/code> and add a new variable, called DB_PORT<\/code>, giving it the value 5435<\/code>.<\/p>\n

With that done, we need to add two extra variables, so that we can authenticate with the database. These are DB_USERNAME<\/code> and DB_PASSWORD<\/code>. The values for these settings will be set from two pre-existing environment variables. These are $PG_USER<\/code> and $PG_PASSWORD<\/code>. Add these in, and we\u2019ve made the required changes for the database.<\/p>\n

Now we need to add a further set of environment variables to support the deployment tool we\u2019ll use, which we\u2019ll see shortly. The deployment environment variables we\u2019ll need are:<\/p>\n