Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Deploy your application in a box - DPC2016
Search
Willem-Jan Zijderveld
June 24, 2016
Programming
0
200
Deploy your application in a box - DPC2016
Willem-Jan Zijderveld
June 24, 2016
Tweet
Share
More Decks by Willem-Jan Zijderveld
See All by Willem-Jan Zijderveld
Deploy je applicatie als een pakketje
wjzijderveld
0
83
Deploy your application in a box - 010PHP
wjzijderveld
0
200
Let's write some history - PHPDay 2016
wjzijderveld
1
240
Let's write some History - PHPBenelux 2016
wjzijderveld
1
270
Event Sourcing in practice @ Qandidate.com
wjzijderveld
1
360
Let's write some history - DPC 2015
wjzijderveld
1
250
Symfony CMF - A Decoupled Content Management Framework
wjzijderveld
0
100
PHPCR: A (better) way to structure content
wjzijderveld
0
160
Other Decks in Programming
See All in Programming
NPOでのDevinの活用
codeforeveryone
0
650
今ならAmazon ECSのサービス間通信をどう選ぶか / Selection of ECS Interservice Communication 2025
tkikuc
20
3.8k
Goで作る、開発・CI環境
sin392
0
190
AIエージェントはこう育てる - GitHub Copilot Agentとチームの共進化サイクル
koboriakira
0
480
Discover Metal 4
rei315
2
110
Benchmark
sysong
0
280
WebViewの現在地 - SwiftUI時代のWebKit - / The Current State Of WebView
marcy731
0
110
datadog dash 2025 LLM observability for reliability and stability
ivry_presentationmaterials
0
410
ruby.wasmで多人数リアルタイム通信ゲームを作ろう
lnit
2
330
たった 1 枚の PHP ファイルで実装する MCP サーバ / MCP Server with Vanilla PHP
okashoi
1
220
PHPでWebSocketサーバーを実装しよう2025
kubotak
0
240
Select API from Kotlin Coroutine
jmatsu
1
210
Featured
See All Featured
For a Future-Friendly Web
brad_frost
179
9.8k
Keith and Marios Guide to Fast Websites
keithpitt
411
22k
Building Flexible Design Systems
yeseniaperezcruz
328
39k
Thoughts on Productivity
jonyablonski
69
4.7k
Writing Fast Ruby
sferik
628
62k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
44
2.4k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
46
9.6k
The World Runs on Bad Software
bkeepers
PRO
69
11k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
229
22k
GitHub's CSS Performance
jonrohan
1031
460k
Measuring & Analyzing Core Web Vitals
bluesmoon
7
500
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
138
34k
Transcript
Deploy your application in a box @willemjanz joind.in/talk/73636
Willem-Jan Zijderveld @willemjanz github.com/wjzijderveld
Don't wait till the last slide with questions
Deployment With the usual disclaimer
It works So why change it?
Can you deploy whenever you want?
Are you ever hesitant to deploy?
"We can't deploy, Robin is sick today"
Do users notice when you deploy?
Things break If you like it or not
Deployments fail • Network issues • Migrations • Broken configuration
Downtime
Missed revenue
Angry customers
Customers losing faith
Scared to deploy
Deployments get postponed
Reserving dedicated time to deploy
Deploying outside office hours...
So what would be a more optimal method?
Less humans
No sweat
More often
0 downtime
Repeatable
Let's get started
Less humans Automate your deploy process to a single step
Possible deployment Migrate database Update code on server (FTP, SSH)
Update code dependencies (composer,npm,bower) Clear cache Reload webserver
> ssh your-server.com > sudo su - > cd /var/www/
> git pull > php composer.phar install > npm install > rm -rf app/cache/* > # Some permission commands > service php-fpm reload Example: before
Example: after > ssh
[email protected]
> ./deploy.sh * Pulling changes
* Updating dependencies * Migrating database * Clearing cache * DEPLOYED NEW VERSION
No sweat Lose the fear of deploying
Testing
Seriously, test your code
New code should have tests
Legacy code? Test the critical parts - Unit tests for
important (domain) logic - Functional tests - Monitor production
Continuous Integration
More often
Smaller changes
6 month projects Deliver something every day Don't wait with
deploying until your feature is ready and approved.
Short lived branches • Allows for rapid deployment • Prevents
huge merge conflicts • Speeds up overall development
Feature toggles
Example: recommendations <?php // BasketController.php function actionBasket(User $user) { $basket
= $this->getBasketOfUser($user); $response = ['basket' => $basket->toArray()]; if ($this->featureIsActive('recommendations')) { $response['recommendations'] = $this->getRecommendations($basket); } return new JsonResponse($response); }
Example: recommendations <?php // BasketController.php function actionBasket(User $user) { $basket
= $this->getBasketOfUser($user); $response = ['basket' => $basket->toArray()]; if ($this->featureIsActive('recommendations')) { $response['recommendations'] = $this->getRecommendations($basket); } return new JsonResponse($response); }
Give some users access
Conditional toggle Check the context against the conditions of the
toggle
Example: Conditional toggle <?php $toggle = new Toggle( 'recommendations', ['user_id'
=> GreaterThan(42)] ); $toggle->active(['user_id' => 21]); // true $toggle->active(['user_id' => 1337]); // false
Example: Conditional toggle <?php $toggle = new Toggle( 'recommendations', ['user_id'
=> GreaterThan(42)] ); $toggle->active(['user_id' => 21]); // true $toggle->active(['user_id' => 1337]); // false
Example: Conditional toggle <?php $toggle = new Toggle( 'recommendations', ['user_id'
=> GreaterThan(42)] ); $toggle->active(['user_id' => 21]); // true $toggle->active(['user_id' => 1337]); // false
Example: Conditional toggle <?php $toggle = new Toggle( 'recommendations', ['user_id'
=> GreaterThan(42)] ); $toggle->active(['user_id' => 21]); // true $toggle->active(['user_id' => 1337]); // false
Feature management GUI API Redis http://labs.qandidate.com/blog/2014/08/19/open-sourcing-our-feature-toggle-api-and-ui/
More often - Smaller iterations - Don't wait for the
whole feature to complete - Make use of feature toggles
0 downtime
Prepare your deployment
Deployment Webserver Application - version 1
Deployment Webserver Application - version 1 Application - version 2
Deployment Webserver Application - version 1 Application - version 2
Deployment Webserver Application - version 1
Deployment Webserver Application - version 1 Install code
Deployment Webserver Application - version 1 Install code Migrations
Deployment Webserver Application - version 1 Install code Migrations Warmup
cache
Deployment Webserver Application - version 1 Install code Migrations Warmup
cache Application - version 2
Deployment Webserver Application - version 1 Install code Migrations Warmup
cache Application - version 2
Example /var /project /releases /20160608-1.0 /20160609-1.1 /current -> /var/project/releases/20160608-1.0
0 downtime - Don't touch the current version - Abort
when any of the steps fail - Make your migrations backwards compatible
Put it in a box
Repeatable
Environment independent
The box In it's simplest form: just a zip
Independent
Reusable On all environments
Some challenges
Filesystem
<!-- services.xml --> <services> <service id="uploader" class="AppBundle\Uploader"> <argument>/var/www/uploads/</argument> </service> </services>
Flysystem Abstract the filesystem - Makes it easier to test
- Makes your code independent of the filesystem, f.e.: - Production uses S3 - Development uses local files
<!-- services.xml --> <services> <service id="uploader" class="AppBundle\Uploader"> <argument type="service" id="oneup_flysystem.private_filesystem"
/> </service> </services>
# config.yml oneup_flysystem: adapters: private_s3: awss3v2: client: aws_s3_client bucket: %s3_private_files_bucket%
filesystem: private: adapter: private_s3
<?php // Uploader.php function uploadAvatar($filename) { $stream = fopen($filename, 'r+');
$this->filesystem ->writeStream('avatars/' . $filename, $stream); if (is_resource($stream)) { fclose($stream); } }
File is now at S3: bucket/avatars/filename. ext
Configuration
# config_prod.yml imports: - { resource: config.yml } doctrine: dbal:
default_connection: default connections: default: driver: pdo_mysql host: 192.168.1.10 dbname: acme_prod user: acme_prod password: SuperSecure
What about staging and acceptance?
Give control to the environment
# config.yml imports: - { resource: parameters.yml } - {
resource: parameters.php } doctrine: dbal: default_connection: default connections: default: driver: pdo_mysql host: %db.hostname% dbname: %db.name% user: %db.user% password: %db.password%
# config.yml imports: - { resource: parameters.yml } - {
resource: parameters.php } doctrine: dbal: default_connection: default connections: default: driver: pdo_mysql host: %db.hostname% dbname: %db.name% user: %db.user% password: %db.password%
# config.yml imports: - { resource: parameters.yml } - {
resource: parameters.php } doctrine: dbal: default_connection: default connections: default: driver: pdo_mysql host: %db.hostname% dbname: %db.name% user: %db.user% password: %db.password%
<?php // parameters.php $parameterMapping = [ 's3_private_files_bucket' => 'MYAPP_S3_PRIVATE_FILES_BUCKET', ];
foreach ($parameterMapping as $parameter => $env) { if (false !== ($value = getenv($env))) { $container->setParameter($parameter, $value); } }
$_ENV['SYMFONY__*'] But those values get overwritten by parameters defined in
config.yml / parameters.yml
PHP dot env https://github.com/vlucas/phpdotenv
<?php // web/index.php $dotenv = new Dotenv\Dotenv(__DIR__ . '/../'); $dotenv->load();
Load .env # .env MYAPP_S3_PRIVATE_FILES_BUCKET=yourbucket
Building the box - Should be reusable - Eliminate hard
dependencies on environment - Give control to the environment
Summary - Less manual steps, eliminate the humans - Lose
the fear: test your stuff - Deploy more often, don't postpone - Deployment shouldn't cause downtime - A deployment should be repeatable
Other questions? @willemjanz Please leave some feedback! joind.in/talk/73636