30 lines
1.3 KiB
Markdown
30 lines
1.3 KiB
Markdown
|
---
|
|||
|
|
id: deploying-drupal-fabric
|
|||
|
|
title: 'Deploying Drupal (and anything else) with Fabric'
|
|||
|
|
type: Talk
|
|||
|
|
slides:
|
|||
|
|
url: ~
|
|||
|
|
embed: ~
|
|||
|
|
video:
|
|||
|
|
embed: ~
|
|||
|
|
url: ~
|
|||
|
|
tags: [meetup, conference, php, fabric, drupal]
|
|||
|
|
meta:
|
|||
|
|
og:
|
|||
|
|
title: Deploying PHP Applcations with Fabric
|
|||
|
|
description: "You've built your PHP application, now learn how to deploy it with Fabric."
|
|||
|
|
type: website
|
|||
|
|
image:
|
|||
|
|
url: /assets/images/talks/deploying-php-fabric.png
|
|||
|
|
width: 1280
|
|||
|
|
height: 800
|
|||
|
|
type: image/png
|
|||
|
|
---
|
|||
|
|
You’ve built your website, and now you just need to deploy it. There are various ways that this could be done - from (S)FTP, to SCP and rsync, to running commands like “git pull” and “composer install” directly on the server (not recommended).
|
|||
|
|
|
|||
|
|
My favourite deployment tool of late is [Fabric][1] - a Python based command line tool for running commands locally as well as on remote servers. It’s language and framework agnostic, and unopinionated so you define the steps and workflow that you need - from a basic few-step deployment to a full Capistrano style zero-downtime deployment.
|
|||
|
|
|
|||
|
|
This talk will cover some introduction to Fabric and how to write your own fabfiles, to then covering some examples and demos of different use case deployments for your Drupal project.
|
|||
|
|
|
|||
|
|
[1]: http://www.fabfile.org
|