---
title: "The Ultimate Guide To Deploying Your PHP Applications"
description: "Learn how to deploy PHP applications on different platforms."
authors:
  - name: "Prosper Otemuyiwa"
    url: "https://auth0.com/blog/authors/prosper-otemuyiwa/"
date: "May 8, 2017"
category: "Developers,Deep Dive,PHP"
tags: ["php", "laravel", "heroku", "deployment"]
url: "https://auth0.com/blog/the-ultimate-guide-to-deploying-php-applications/"
---

# The Ultimate Guide To Deploying Your PHP Applications



**TL;DR:** There is a popular mantra amongst developers that goes like this *write, test and deploy*. In this tutorial, I'll show you how to deploy your PHP apps to different cloud server platforms such as [Google Cloud](https://cloud.google.com), [Microsoft Azure](https://azure.microsoft.com), [Heroku](https://heroku.com), [IBM Bluemix](https://www.ibm.com/cloud-computing/bluemix), and others.

---

## Introduction to Cloud Server

Cloud servers are basically virtual servers that run within a cloud computing environment. There are various benefits to hosting and deploying your applications on the cloud. They are:

- Economically efficient.
- You have the freedom to modify the server software to your needs.
- Cloud servers scale very well.
- Stability and security.

In fact, many companies have moved their infrastructure to the cloud in order to reduce cost and complexity. It's a great option for small, mid-sized, and enterprise scale businesses. If you write a lot of tutorials and do POCs (Proof-of-concepts) like me, it's also a great choice for you!

A generic PHP application involves the common *LAMP (Linux, Apache, Mysql and PHP)* stack.

- **Linux:** The operating system that runs the other software packages.
- **Apache:** The web server that runs the PHP code. A popular alternative software is *Nginx*.
- **MySQL:** The database. A popular alternative software is PostgreSQL.
- **PHP:** The server-side language for building the application.

Next, let's cover how to deploy php applications to several cloud server platforms.

## Heroku

Heroku is a cloud platform that helps you deploy and host your applications the modern way. It does all the heavy-lifting for you. Let's quickly take a look at how to deploy and maintain a PHP application on heroku.

![PHP-Heroku Architecture](https://images.ctfassets.net/23aumh6u8s0i/1ZsQy6m9ZhfxDZiGjPlZ31/f038ff9c7e1096b40ee413781c84bcee/php-heroku-architecture)
_PHP Heroku Architecture_

If you don't have an account, go ahead and create one on [heroku.com](https://www.heroku.com/). Go ahead and install the [heroku cli](https://devcenter.heroku.com/articles/heroku-cli). Once you have that installed, go ahead and clone this simple [starwars PHP application](https://github.com/auth0-blog/starwars-phpapp).

> Heroku runs your PHP app in a dyno, a smart container which provides a modern stack with your choice of web server(Apache or Nginx) and runtime(PHP or HHVM).

Make sure you follow these steps below:

- Create a `.env` file from `.env.example`.
- You need to have an account with [Auth0](https://auth0.com/signup).
- Go to your [Auth0 Dashboard](https://manage.auth0.com/#/) and click the "create a new client" button.
- Name your new app and select "Regular Web Applications".
- In the Settings for your new Auth0 client app, add `http://localhost:8000` to the Allowed Callback URLs.
- Copy out your *client id*, *client secret*, *domain* and *callback url*. Ensure you assign them to the right variables in your `.env` file.

> [Auth0 offers a generous **free tier**](https://auth0.com/pricing) to get started with modern authentication.

Now, we have a `composer.json` file which contains the list of packages that the application needs. Go ahead and run `composer install` on your local machine to install these packages. Get [composer here](https://getcomposer.org/download/) if you don't have it installed already.

Go ahead and run the app. The app should be running like so:

![Landing page](https://images.ctfassets.net/23aumh6u8s0i/7IjDW0NluWVJd6HWujIGsJ/1485619afabffc066f4390b2408ed810/landing)
_Landing page_

![Logged In User](https://images.ctfassets.net/23aumh6u8s0i/3GRfjny20SGo6nmwPwtCfy/dce680018765fc3c6d0a654ff2cdef93/welcome)
_Logged In User_

Awesome! Our app works locally. Time to deploy! The first thing we'll do is to add a `Procfile` to the root directory of our app.

Create a new file called `Procfile` without any file extension and add this:

```bash
web: vendor/bin/heroku-php-apache2
```

>A Procfile is a text file in the root directory of your application that defines process types and explicitly declares what command should be executed to start your app on heroku.

If you are interested in using *Nginx* as the web server, then the content of your *Procfile* would be:

```bash
web: vendor/bin/heroku-php-nginx
```

Now that you have added the Procfile, go ahead and upload the project to [GitHub](https://github.com) or [Bitbucket](https://bitbucket.org/). Mine is [starwazapp](https://github.com/unicodeveloper/starwazapp).

Head over to [dashboard.heroku.com/apps](https://dashboard.heroku.com/apps) and create a new app like so:

![Create a new app](https://images.ctfassets.net/23aumh6u8s0i/2guwE26bWbn2iezmhPk8dd/f8398d47264bfee02e4c912a898eb7bb/create_new_app)
_Create a new app from the dashboard_

Give it a name like so:

![Give the app a name](https://images.ctfassets.net/23aumh6u8s0i/7083ETGlQyhwRN96QziS2H/3a98c6c95e595d5253bb3a926bf1dfdc/giveappaname)
_Give app a name_

Choose a deployment method. In our case, we'll use GitHub like so:

![Connect to GitHub](https://images.ctfassets.net/23aumh6u8s0i/3slM12HrXz3UgIkugad20I/3588e4015c4449afdf544416505ac9c3/connecttogithub)
_Connect to GitHub_

> The reason for choosing GitHub is to make development and maintenance process very smooth. Developers can work on new features using the git workflow.

Now, type the name of the repo in the circled area and click **Search**. Heroku will search for your repo under your GitHub account and display it like so

![Search for repo](https://images.ctfassets.net/23aumh6u8s0i/uLFGYKIpu73EG0NuEVRXT/e674104eb929156cf2bc3d49c9dea3cf/searchforrepo)
_Search for repo_

Click on `connect` like so

![Click on connect](https://images.ctfassets.net/23aumh6u8s0i/7LaKWhNN2wtGpydv4B9ApW/dd8e1e2a01b399ef3fa2b307231b1bb6/clickonconnect)
_Click on the connect button_

Heroku will connect the repo like so

![Connected repo](https://images.ctfassets.net/23aumh6u8s0i/5ed28U6082SCvSsTk7mipF/16a769e0bd525f92d28e1146649b8415/connected)
_Connected Project_

Scroll down a bit. This is the interesting part. Heroku allows you to enable automatic deploys with the push of a button. It also gives you an option to wait for your continuous integration process to pass before deploying to production. In a real world app, you'll have a test suite for your codebase. A developers' code runs against the test suite. If it passes, the code will be pushed to production.

![Option to enable deploy](https://images.ctfassets.net/23aumh6u8s0i/5CKBckjILl5rU5Dm6MtqWR/312de3c7ad340a9ee085761df5821419/enabling_deploy_button)

Click to enable automatic deploys. We don't have any CI service, so we don't need to enable that option. Now, let's deploy the master branch.

> **Note:** You can have other branches and specify which branch you want for production. In our case, the master branch is the prod. branch.

Click on the **Deploy branch**. Heroku will scan through your `composer.lock` file, install the necessary packages and deploy!

![Deploy](https://images.ctfassets.net/23aumh6u8s0i/7muEv2TMASjdmZ5rNgb81G/d02555f6e2039cd15f45da9d4314bd85/deployprocess)
_Deploy finally_

Click on the **View** button to check out your app.

![Ooops](https://images.ctfassets.net/23aumh6u8s0i/67ZmmZmU6wEiGtaNnsadwP/c3645770f7d436325ff7009c1f134ce9/herokuoops)
_Error 500_

Ooops! We are experiencing a 500 error. Aha, we haven't set any environment variables yet. Locally, we had a `.env` file. On heroku, there is no `.env` file, but there is a way to set environment variables. Go to **Settings** on your dashboard and add them as config variables like so:

![Add config variables](https://images.ctfassets.net/23aumh6u8s0i/3mmv5ots7jGi2naJ7PrTg7/40b74a0bce675783267328909d9b247f/config_variable)

Oh, one more thing! The new callback url in my case is `http://starwazapp.herokuapp.com`. Make sure you add your new callback url to the *Allowed Callback URLs* in your [Auth0 dashboard](https://manage.auth0.com).

Your app should be live & working now!

![App working](https://images.ctfassets.net/23aumh6u8s0i/7JqpDq7C0EBw2hOIRuQOhy/d62208dc6fb5f3ddd3aef80a9d8cb644/appworking)
_Live App_

### Make a small change

Let's make a small change to our app and see how effortlessly it deploys it to production.

Open `index.php` and change the content of the `<p>` tag from `Heard you don't want to migrate to PHP 7? Dare us!` to `Star Wars - The Awakening!`. Commit and push to your master branch. Now, go to the **Activity** tab of your Heroku Dashboard and notice the build. Reload your app and you'll see the difference.

![Build Succeeded](https://images.ctfassets.net/23aumh6u8s0i/3Wr715spzdvdXRWKwMJrDm/8d738342443b2e997f95b47aff67f28e/build_succeeded)
_Build Succeeded_

![New version of app](https://images.ctfassets.net/23aumh6u8s0i/1BdieR8ePbDIbpDKyjQWFQ/a17d3ee23b903b5c5a825cf248568f00/starwarzawakening)
_New version_

### Database, Caching & Cron Jobs

Let's quickly talk about how to handle database, caching and cron jobs. On heroku, you can use [ClearDB](http://w2.cleardb.net/) and [Postgres](https://elements.heroku.com/addons/heroku-postgresql) with PHP. Add ClearDB to your app like so:

```bash
heroku addons:create cleardb:ignite
```

This command provisions a new ClearDB database returns the URL that the app will use to access it. All you simply need to do is add it to your app as an environment variable and parse it in your app config like so:

> ClearDB is a powerful, fault tolerant database-as-a-service in the cloud for your MySQL powered applications.

```php
<?php
$url = parse_url(getenv("CLEARDB_DATABASE_URL"));

$server = $url["host"];
$username = $url["user"];
$password = $url["pass"];
$db = substr($url["path"], 1);

$conn = new mysqli($server, $username, $password, $db);
?>
```
_using mysqli_

You can tweak that to suit PDO style. Add Postgres to your app like so:

```bash
heroku addons:create heroku-postgresql:hobby-dev
```

Head over to the [addons](https://elements.heroku.com/addons), you'll see other kinds of databases that you can use with your PHP app.

Heroku provides an array of addons for caching, from `memcache` to `fastly` to `ironcache` and others. You can check out how to use [memcache with PHP on heroku](https://devcenter.heroku.com/articles/memcachedcloud#using-memcached-from-php).

Finally, you can use the [Heroku Scheduler](https://devcenter.heroku.com/articles/scheduler) for running jobs on your app at scheduled time intervals.

## Google Cloud

The [Google Cloud platform](https://cloud.google.com) is a giant and trusted cloud platform that a lot of companies all over the world have adopted in deploying and hosting their apps. Your apps will be running on the same infrastructure that powers all of Google's products. What other form of confidence do you need to assure you that your application will scale well enough to serve your thousands and millions of users easily?

Google Cloud offers different options for hosting PHP apps. The platform offers [App Engine (Full managed)](https://cloud.google.com/appengine/), [Compute Engine (Scalabe VMs)](https://cloud.google.com/compute/) and [Container Engine (Kubernetes Clusters)](https://cloud.google.com/container-engine/).

In our case, we'll use App Engine. It abstracts the infrastucture away. Let's jump into deploying our famous **Star Wars** app to Google App Engine.

When using Google App Engine, you can choose the **Standard** or **Flexible** environment. The latter, like the name implies allows you to install any PHP extension that works on Debian Linux, has a configurable Nginx web server, writable filesystem, latest PHP versions and allows you to run deployment scripts using `composer.json`.

We'll use the flexible environment. So, go ahead and [create a new project](https://console.cloud.google.com/projectselector/appengine/create?lang=flex_php&st=true). Click on **Create**, give the project a name, select the region you'll like to serve your app and enable billing.

> **Note:** You won't be charged without your permission.

Now, download the [Google SDK](https://cloud.google.com/sdk/docs/) and install the Google Cloud tools.

![Installing Google SDK](https://images.ctfassets.net/23aumh6u8s0i/5gBU7Gl6LzWjJxKKNFEqZ2/c0314ba776e1b9d96a38ddc290b83312/install)
_Installing Google SDK_

![Running gcloud](https://images.ctfassets.net/23aumh6u8s0i/6EiHLi3PzPxxjt2FMOfsmH/89a7cc3ec5c29a899e49e1a4daf791e9/cloudinit)
_Running gcloud_

Go ahead and create an `app.yaml` file in the root of our project like so:

_app.yaml_

```bash
runtime: php
env: flex
```

So, our `.env` file has been pushed to Google Cloud. An alternative to using that is to add the environment variables to the `app.yaml` file like so:

```yaml
...
env_variables:
  # The values here will override those in ".env". This is useful for
  # production-specific configuration. However, feel free to set these
  # values in ".env" instead if you prefer.
  APP_LOG: errorlog

```

Now, deploy your application from your console by running `gcloud app deploy`.

**Note:** Now grab the URL, in my case it is `https://starwars-166515.appspot.com/` and add to **Allowed Origins(CORS)** and **Allowed Callback URLs** in your [Auth0 dashboard](https://manage.auth0.com). Also add the URL to `AUTH0_CALLBACK_URL` in your `.env` file.

Run `gcloud app deploy` again to provision a new version of the app. Check out your app now. It should be live like so:

![Live App](https://images.ctfassets.net/23aumh6u8s0i/6aTcdrxzAtuuffCvSlIecI/bfefb72938e46df6d4c1de86a414ba0a/landingpage)
_Live App_

### Database, Caching & Cron Jobs

Google Cloud provides a Cloud SQL Instance platform. Check out how to [configure, connect and create MySQL instances for your app](https://cloud.google.com/sql/docs/mysql/create-instance).

Oh, You can also use [phpMyAdmin](https://www.phpmyadmin.net/) on [Google App Engine](https://cloud.google.com/sql/docs/mysql/phpmyadmin-on-app-engine).

Google App Engine includes implementations of the standard [Memcache](http://php.net/manual/en/book.memcache.php) and [Memcached](http://php.net/manual/en/book.memcached.php) APIs. Check out how to use [Memcache in your app on Google Cloud](https://cloud.google.com/appengine/docs/standard/php/memcache/using).

The App Engine Cron Service allows you to configure regularly scheduled tasks that operate at defined times or regular intervals. Check out how to [schedule cron jobs and use task queues with PHP on Google Cloud](https://cloud.google.com/appengine/docs/standard/php/config/cron).

It's relatively easy to deploy [Laravel](https://cloud.google.com/community/tutorials/run-laravel-on-appengine-flexible), [Symfony](https://cloud.google.com/community/tutorials/run-symfony-on-appengine-flexible) and [Wordpress](https://cloud.google.com/php/tutorials/wordpress-app-engine-flexible) apps to the Google Cloud Platform.

## IBM BlueMix

IBM Bluemix allows you to easily configure, deploy and scale on a powerful, high performance global cloud infrastructure. Let's jump into deploying our famous **Star Wars** app to IBM Bluemix.

[Sign up on Bluemix](https://console.ng.bluemix.net/registration/) like so:

![BlueMix Signup](https://images.ctfassets.net/23aumh6u8s0i/7aC4SW9Z5qX8Ez4Q1YSFqv/24c0d08de518d7c88258fc3d041b0713/signup)
_Signup on Bluemix_

> **Note:** The Bluemix platform offers a 30-day free trial so you have a chance to try deploying your own application before handing over your credit card details.

Go ahead and create an organization and space. I named my space `prod`.

![Dashboard](https://images.ctfassets.net/23aumh6u8s0i/wCd1siD3dafCk11nOwG0N/acb3ab0a026ec58e0139c0bd09fbe3fc/dashboard)

Now, go ahead and install the [Cloud Foundry CLI](https://github.com/cloudfoundry/cli#downloads). Once you have done that, go head and login from your terminal like so:

```bash
cf api https://api.ng.bluemix.net/
cf login
```

![Authenticating via the terminal](https://images.ctfassets.net/23aumh6u8s0i/b0Qz2KqWOhwsRcclvrVXO/d96631c05b906e098f1b5b0f9e6fc6af/authenticate)
_Log in to Bluemix_

The next step is to create a `manifest.yml` file in the root directory of the app. The `manifest.yml` includes basic information about your app, such as the name, how much memory to allocate for each instance and the route. Our manifest file should look like so:

```bash
---
applications:
  - name: starwarsapp
    memory: 512M
    instances: 1
    host: starwarsapp
```

You can also explicitly specify the buildpack in the manifest file. Thankfully, Cloud Foundry automatically detects which [buildpack](https://github.com/cloudfoundry/php-buildpac) is required when you push an app.

> Buildpacks provide framework and runtime support for your applications. Buildpacks typically examine user-provided artifacts to determine what dependencies to download and how to configure applications to communicate with bound services.

Finally, deploy your app by running the following command like so:

```bash
cf push <yourapp>
```

`<yourapp>` has to be a unique name.

![Starting Deploy](https://images.ctfassets.net/23aumh6u8s0i/XazQJCReozamoiKGbUHiY/b32c7c1a074a7f1dcb8b9c053bed2845/starting_deploy)
_Starting Deploy_

![Ending Deploy](https://images.ctfassets.net/23aumh6u8s0i/7jRuqsrw95KuX5Tu9ATQkm/6e948c8032c9e7def790d142e4dfeb20/ending_deploy)
_Ending Deploy_

Try to run the app now. In my case, the url is `starwarsapp.mybluemix.net`. Oops, a 500 error. We haven't loaded our environment variables yet. How do we do that with Bluemix.

You can either use the Cloud Foundry CLI or the Bluemix user interface to set environment variables. Let's use the Bluemix user interface. So, follow the steps below:

- Open the Bluemix [dashboard](https://console.ng.bluemix.net/dashboard/apps/).

  ![Dashboard - App running](https://images.ctfassets.net/23aumh6u8s0i/3dbyMP8c53rATONYrm5JQ9/9e17232cb5b23feef2b913ad2cf34f8d/dashboardapprunning)

- Click on the app. You'll be redirected to another page with more details about the app.
- Select **Runtime** from the left panel.

  ![Click on Runtime](https://images.ctfassets.net/23aumh6u8s0i/7DsUWLvB3oXFfhOMErZtYI/bcc9862412240216a01162ddc2c5b6b4/select_runtime)

-  Now, click on **Environment variables** tab like so

  ![Select Environment Variables](https://images.ctfassets.net/23aumh6u8s0i/6MdigmJiHoyfq8iVaVSrSy/22b43a4dd3c280d7824e57220b074971/select_environmentvariable)

- Scroll down and click the **Add** button to add the environment variables like so

  ![Add environment variables](https://images.ctfassets.net/23aumh6u8s0i/2Mk9adOEdiiPfkX537Gx3x/f25c73418c6927cebc8b1c77d12325d2/add_env_variables)

- Click the `Save` button. Once you do that, your app will restart automatically.

**Note:** Now grab the URL, in my case it is `https://starwarsapp.mybluemix.net/` and add to **Allowed Origins(CORS)** and **Allowed Callback URLs** in your [Auth0 dashboard](https://manage.auth0.com).

Now check out your app. Your app should be live!

### Database, Caching & Cron Jobs

Cloud Foundry provides the ability to create services. IBM Bluemix offers the Cloudant NoSQL database(the Bluemix name for CouchDB). So, you can use the `cf` tool to create database services like so:

```bash
cf create-service cloudantNoSQLDB Lite starwarsapp
```

IBM Bluemix also offers the ClearDB MySQL service. So, you can use the `cf` tool to create one like so:

```bash
cf create-service cleardb spark starwarsapp
```

They offer [MongoDB](https://new-console.stage1.ng.bluemix.net/catalog/services/compose-for-mongodb/), [PostgreSQL](https://new-console.stage1.ng.bluemix.net/catalog/services/compose-for-postgresql/), [RethinkDB](https://new-console.stage1.ng.bluemix.net/catalog/services/compose-for-rethinkdb/).

You can always use the Cloud Foundry tool to check out a lot of things such as logs, environment variables like so:

- `cf logs --recent yourapp` - Shows the logs of your apps.
- `cf env yourapp` - Shows the environment variables associated with your app.
- `cf marketplace` - Shows all the services that Bluemix has to offer.

IBM Bluemix also offers [Redis Cloud](https://console.ng.bluemix.net/catalog/services/redis-cloud), a fully-managed cloud service for hosting and running your Redis dataset in BlueMix in a highly-available and scalable manner.

IBM Bluemix provides the [**Workload Scheduler**](https://console.ng.bluemix.net/catalog/services/workload-scheduler) service. This service allows you to integrate your application with the capability to schedule workflows. Far beyond Cron, exploit job scheduling within and outside Bluemix. Easily create workflows in your application to run on a regular basis, at a specific time, on event basis (for example, when a file is deleted or updated), according to your needs. You can either use the *Workload Scheduler User Interface* or use the APIs.

Get started with [Scheduling Jobs here](https://console.ng.bluemix.net/docs/services/WorkloadScheduler/index.html).

Oh, one more thing, here is how to [deploy your Laravel app on IBM Bluemix](https://www.ibm.com/blogs/bluemix/2014/06/getting-started-laravel-bluemix/).

## Microsoft Azure

Microsoft Azure is another massive cloud platform that allows you to scale your apps easily. Let's get started with deploying our Star Wars app on Azure.

With Microsoft Azure, you can deploy via:

- FTP.
- Syncing with a cloud folder.
- Local Git.
- Cloud based source control service such as GitHub or Bitbucket.

In our case, we'll set up deployment with Git.

1. First, create an [account with Microsoft Azure](https://portal.azure.com).

    ![Dashboard](https://images.ctfassets.net/23aumh6u8s0i/3FCtLMHGcWOFXxsiAaBSof/944296323cb9da8ccd344d1a978186f5/dashboard)
    _Dashboard_
2. Click on **New** on the left panel.
3. Click **See all** just next to Marketplace.
4. Click **Web + SQL**, then go ahead and create.

    ![Web + SQL](https://images.ctfassets.net/23aumh6u8s0i/6XAHS0pkRv7w54sgwZnViW/45cf664d2c4684a743232028c4898d0f/websql)

5. You'll be prompted to select an offer for the type of subscription you are comfortable with. I chose *Free Trial*. With that, you'll be given a $200 Azure Credit.
6. Give your name an app, then create an SQL database. Well, it's not needed for our app but for some reasons Azure forces you to create it.

    ![Create a new app](https://images.ctfassets.net/23aumh6u8s0i/4TRZsohKIbOetjnB4Tqe2R/85d7c62100a5c6671b883e2e785ee69d/createnewapp)
    _Create a new app_

7. Now that our app has been created. Click on **App Services** by the left panel to see your app.

    ![App services](https://images.ctfassets.net/23aumh6u8s0i/uosZZ0b17PmlEh0U7S0Sd/8d4a86dac2179fc7eebc8ba5e2b80296/appservices)
    _New app_

8. Click on the app, choose *Deployment options*, then click on `GitHub`.
9. Authorize GitHub to access your repo. Choose the Project. Choose the branch. In my case, I have an `azure` branch. That's the branch I'll use for deploying my code to the Azure platform.

    ![Configuration on your app](https://images.ctfassets.net/23aumh6u8s0i/6LfW5VhsyTT5qLreGsWijj/9dab7bd3c4ac07d306925da7017a7d00/configuration)

10. Check out the deployment notifications.

    ![Deployment Notifications](https://images.ctfassets.net/23aumh6u8s0i/3wDhJHItvmc2OiWPvJJjaR/5b0fcab370c680483f54f428351c4cf8/deployment_notifications)

    Now, browse to `http://[yoursitename].azurewebsites.net`. In my case, it is `http://starwarzapp.azurewebsites.net`.

    Oops!, there is an HTTP 500 error. What's happening? Okay, we need to set the environment variables.

11. Go to your app in **App Services**, Click on **Application Settings** and then add the environment variables by the right.

    **Note:** Now grab the app URL, in my case it is `http://starwarzapp.azurewebsites.net/` and add to **Allowed Origins(CORS)** and **Allowed Callback URLs** in your [Auth0 dashboard](https://manage.auth0.com).

12. By default, azure deployment doesn't do anything with our `composer.json` or `composer.lock` file. So, no package is getting installed. Now go back to **App Services**, click on your app, then go to **Development Tools** and select **Extension**. Choose the `Composer` extension and agree to the legal agreements.

    ![Add extension](https://images.ctfassets.net/23aumh6u8s0i/2bKEKMk4YETjvpjRkvo2ui/1fc99da555947a9dd03c3d10fd5ed8d1/addextension)

13. Now, make a little change to your app and push again to GitHub. You should see it deploying like so:

    ![Make a change](https://images.ctfassets.net/23aumh6u8s0i/5WiNopUmZUk355Scv2zArV/42f30367f5fab1ef86b49e51504b550b/make_a_change)

    ![Deployment details](https://images.ctfassets.net/23aumh6u8s0i/4WHJTfbRTTPBnktoWH6bXt/80e591bfdc99fc39077bb54959fcf9eb/deploymentdetails)

14. Now check out your app again. It should be [live](http://starwarzapp.azurewebsites.net) & working!

    ![Landing Page](https://images.ctfassets.net/23aumh6u8s0i/5t9grDkjpCiKYiUjg4qlzM/8f3aa4404080bed97b77c517d0a27524/landingpage)

### Database, Caching & Cron Jobs

Microsoft Azure offers *Azure Redis Cache*. It is based on the popular open source Redis cache. It's easy to create and use like so:

1. Click **New > Data + Storage > Redis Cache**.
2. Enter the name of the cache, select the region and create it.

Check out the [documentation](https://azure.microsoft.com/en-us/services/cache) on how to use it.

For scheduling and running tasks, Azure offers a [Scheduler](https://azure.microsoft.com/en-us/services/scheduler/). It allows you to:

- Call services inside or outside of Azure.
- Run jobs on any schedule.
- Use Azure Storage queues for long-running or offline jobs.
- Invoke Azure Service Bus queues.

Check out [how to create and manage jobs using the Scheduler](https://docs.microsoft.com/en-us/azure/scheduler/scheduler-get-started-portal).

We already talked a little about setting up a database earlier while we were deploying our app, but let's quickly look at how to setup a MySQL database.

1. Log into the Azure Portal.
2. Click **New** on the left panel of the dashboard. Choose **Data + Storage** in the Marketplace, then select MySQL database.
3. Go ahead and configure your new MySQL database. Enter a name, choose your subscription, location and fill the required fields. Create!
4. Connect to the database.

    ![The connection info](https://images.ctfassets.net/23aumh6u8s0i/deQpiFk8ef3hIJmM3Rn5F/fe66841281f5b21ca01f6470a433585d/create-db-5-finished-db-blade)

Laravel developers can easily [configure a MySQL database for their apps on Azure](https://docs.microsoft.com/en-us/azure/store-php-create-mysql-database).

## Amazon Web Services

More companies use AWS(Amazon Web Services) for storing all sorts of data ranging from images, mp3 files to videos than any other cloud platform. In fact, a lot of organizations like Uber, Spotify, Salesforce use Amazon Web Services wholy for hosting, deployment and infrastructure. AWS has a ton of developer products.

The service we'll use for deploying our famous StarWars app is **Amazon Elastic Beanstalk**. Let's get started.

- Sign up for an [AWS account](https://aws.amazon.com/account/) if you don't have one.
- Head over to [Elastic Beanstalk console](https://us-west-2.console.aws.amazon.com/elasticbeanstalk).
- Create a new app.
    ![Create new app](https://images.ctfassets.net/23aumh6u8s0i/5ALULfcaxqCd7mVqoYxiqq/9f5e32f3e1e8a5d91f2fad3601f74281/createnewapp)
- Click on `create web server`.
    ![Create web server](https://images.ctfassets.net/23aumh6u8s0i/56TD8zLXu0zXzDOm9VCtrc/9cae50312050414671e41c025b2bd905/createwebserver)
- Create the webserver environment.
    ![Environment type](https://images.ctfassets.net/23aumh6u8s0i/62g9PZpgNBrpJR5LE4Aig7/e8b9acff1b36961ba5a1e13a3a6c76ee/environmentype)
- Upload your code. Elastic Beanstalk requires that you upload a zip file of your codebase. You can manually zip it up. But I prefer to do that from my terminal like so:

    ```bash
     zip ../starwarsapp.zip -r * .[^.]*
    ```
- Now, upload it to AWS like so:
    ![Upload code to AWS](https://images.ctfassets.net/23aumh6u8s0i/4xPQmKHbwq6kR4ZWt9ui4s/339e2697498c3725fc71766bd35e32bd/uploadcode)
- Check availability for the app URL. Mine looks like this:
    ![URL](https://images.ctfassets.net/23aumh6u8s0i/3va42kq9BZuyN1t9g2xjRc/6aa9107b110e8fe6052f3bc1579ed2eb/url)
- The next page allows us to configure Database Instance. Now our app doesn't require one, so we can skip it.
    ![Skip setting up DB Instance](https://images.ctfassets.net/23aumh6u8s0i/1PvzfXmXw3kvBSmYeDOPxv/4d42b18d539178439c0c91fe18fc84b7/skip)
- This step allows to modify our configuration details. The default one is okay for our app.
    ![Configuration details](https://images.ctfassets.net/23aumh6u8s0i/50XGIGN5RGf0jPphAo66mj/740cd0b4580bb80a49d8018d6f9daec8/config)
- Now, add your environment variables like so:
    ![Environment Variables](https://images.ctfassets.net/23aumh6u8s0i/4gw0KtVcAVLT69E230P9t1/757dc484d6a19e352b2e59eb8bbf1478/environment_vars)

  **Note:** Now grab the URL, in my case it is `http://starwarzapp.us-west-2.elasticbeanstalk.com` and add to **Allowed Origins(CORS)** and **Allowed Callback URLs** in your [Auth0 dashboard](https://manage.auth0.com). Ensure that you add it as an environment variable in Elastic Beanstalk too.

- Add Permission like so:
    ![Permission](https://images.ctfassets.net/23aumh6u8s0i/3j8hI1JnT963t5sNO27t3h/73fdb2d360cddb6b6c3158f5a33699d8/permission)
- Review the information before launching.
    ![Review](https://images.ctfassets.net/23aumh6u8s0i/1jfd0CCWwVSmrKVWQyQA95/199c52c3eaf64f2415b556b771661c2a/review)
- Launch.

![Deployed](https://images.ctfassets.net/23aumh6u8s0i/5s3ZLjJGtq3cn05I0QqQWz/6af2db1877384bc151463fb23b8e4c0e/deployed)

![Live app](https://images.ctfassets.net/23aumh6u8s0i/2ORqV2dJT3dnSJ5krmOQtO/6deef71d62fd685658f9e382d3d48a3a/landingpage)
_Live app_

Check out how to deploy:

- [A Laravel app to Elastic Beanstalk](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/php-laravel-tutorial.html).
- [A CakePHP app to Elastic Beanstalk](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/php-cakephp-tutorial.html).
- [A Symfony2 app to Elastic Beanstalk](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_PHP_symfony2.html).
- [A Wordpress website to Elastic Beanstalk](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/php-hawordpress-tutorial.html).
- [A Drupal website to Elastic Beanstalk](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/php-hadrupal-tutorial.html).

### Database, Caching and Cron Jobs

You can use an Amazon Relational Database Service (Amazon RDS) DB instance to store data gathered and modified by your application. The database can be attached to your environment and managed by Elastic Beanstalk, or created and managed externally. Check out how to [easily add a DB instance to your app](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_PHP.rds.html).

For caching, Amazon Web Services offers [ElastiCache](https://aws.amazon.com/elasticache). It is a web service that makes it easy to deploy, operate, and scale an in-memory data store or cache in the cloud. Amazon ElastiCache supports two open-source in-memory engines:

- [Redis](https://aws.amazon.com/elasticache/redis).
- Memcached.

Amazon ElastiCache automatically detects and replaces failed nodes, reducing the overhead associated with self-managed infrastructures and provides a resilient system that mitigates the risk of overloaded databases, which slow website and application load times. Through integration with [Amazon CloudWatch](https://aws.amazon.com/cloudwatch), Amazon ElastiCache provides enhanced visibility into key performance metrics associated with your Redis or Memcached nodes.

Companies like [AirBnb](https://www.airbnb.com), [Healthguru](http://www.healthguru.com), [PlaceIQ](http://www.placeiq.com) and [Tokyo Data Network](http://www.tdn.co.jp) use ElastiCache for caching at multiple layers spanning HTML fragments, results of expensive DB queries, ephemeral session data and search results.

> Check out [how to install the ElastiCache Cluster Client for PHP here](http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/Appendix.PHPAutoDiscoverySetup.html).

Here is an [excellent post on building a PHP visitor counter with ElastiCache and Elastic Beanstalk](https://linuxacademy.com/howtoguides/posts/show/topic/13716-php-visitor-counter-with-elasticache-and-elastic-beanstalk)

You can set up a cron job on Elastic Beanstalk. Learn how to run cron jobs on [Amazon Web Services(AWS) Elastic Beanstalk](https://medium.com/@joelennon/running-cron-jobs-on-amazon-web-services-aws-elastic-beanstalk-a41d91d1c571).

## Laravel Forge

[Laravel Forge](https://forge.laravel.com) , created by [Taylor Otwell](https://twitter.com/taylorotwell) is a platform that helps you deploy and launch your application in minutes. It does the heavy-lifting for you. Forge takes care of provisioning your servers on popular cloud hosting providers such as Linode, Digital Ocean and AWS. It was initially built for Laravel apps, but now it has support for virtually any PHP application.

![Laravel Forge](https://images.ctfassets.net/23aumh6u8s0i/6aAcSOgPoGkwbXZEquyUge/3a4029a0d0aec599c451a63d6a5d9e93/laravelforge)
_Laravel Forge_

Laravel Forge allows you to easily do the following apart from provisioning servers:

- It integrates with LetsEncrypt to generate Free SSL Certificates for your apps.
- Easily manage jobs and queues.
- Collaboration with your team by sharing your server's management dashboard with co-workers.

Matt Stauffer has an [amazing post on deploying your first Laravel app to Forge](https://mattstauffer.co/blog/getting-your-first-site-up-and-running-in-laravel-forge).

James Fairhurst also has a [great guide on using Laravel Forge to setup an AWS Server](https://medium.com/@james_fairhurst/using-laravel-forge-to-setup-an-aws-server-7da83f760a56).

Finally, the most popular educational PHP platform, [laracasts.com](https://laracasts.com) has a [series on server management with Forge](https://laracasts.com/series/server-management-with-forge)

## Envoyer

[Envoyer](https://envoyer.io) is a platform that allows zero downtime PHP deployment. It allows you integrate with various services such as Gitlab, Slack, Bitbucket e.t.c.

With Envoyer, you can perform:

- Seamless Deployment rollbacks.
- Deploy to multiple servers.
- Monitor Cron Jobs.
- Perform Application Health Checks.

## Deployer

[Deployer](https://deployer.org) is a deployment tool for PHP. It allows you to do the following:

- Run tasks in parallel.
- Atomic deploys.
- Rollbacks.
- Create deployment scripts in form of recipes.

It works with *Laravel*, *Symfony*, *CakePHP*, *Yiiframework*, *Zend*, *FuelPHP*, *Drupal*, *Wordpress*, and *Magento*. Check out this [excellent article on deploying PHP applications with Deployer](https://www.sitepoint.com/deploying-php-applications-with-deployer).

## Conclusion

There is no way we can cover all the different options available for deploying PHP applications. PHP is an enterprise language that has evolved over the years, thus calling for more efficient ways for deploying PHP apps from a local machine to production. Hopefully, this guide covers all your basic needs for deploying your PHP apps to all the major cloud providers. However, there is another resource I recommend for extensive knowledge in [learning to deploy PHP applications](http://www.deployingphpapplications.com).

> Auth0 provides the simplest and easiest to use [user interface tools to help administrators manage user identities](https://auth0.com/user-management) including password resets, creating and provisioning, blocking and deleting users.

How have you been handling your deployments? Please, let me know in the comments section below!