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
210
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
0から始めるモジュラーモノリス-クリーンなモノリスを目指して
sushi0120
0
170
LLMは麻雀を知らなすぎるから俺が教育してやる
po3rin
2
1.3k
QA x AIエコシステム段階構築作戦
osu
0
210
[DevinMeetupTokyo2025] コード書かせないDevinの使い方
takumiyoshikawa
2
220
[Codecon - 2025] Como não odiar seus testes
camilacampos
0
100
レトロゲームから学ぶ通信技術の歴史
kimkim0106
0
140
AIに安心して任せるためにTypeScriptで一意な型を作ろう
arfes0e2b3c
0
270
[SRE NEXT] 複雑なシステムにおけるUser Journey SLOの導入
yakenji
0
810
顧客の画像データをテラバイト単位で配信する 画像サーバを WebP にした際に起こった課題と その対応策 ~継続的な取り組みを添えて~
takutakahashi
4
1.4k
DMMを支える決済基盤の技術的負債にどう立ち向かうか / Addressing Technical Debt in Payment Infrastructure
yoshiyoshifujii
4
640
なぜあなたのオブザーバビリティ導入は頓挫するのか
ryota_hnk
3
510
構文解析器入門
ydah
7
1.9k
Featured
See All Featured
Learning to Love Humans: Emotional Interface Design
aarron
273
40k
Building a Modern Day E-commerce SEO Strategy
aleyda
42
7.4k
Connecting the Dots Between Site Speed, User Experience & Your Business [WebExpo 2025]
tammyeverts
8
390
Fashionably flexible responsive web design (full day workshop)
malarkey
407
66k
The World Runs on Bad Software
bkeepers
PRO
70
11k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
8
720
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
RailsConf 2023
tenderlove
30
1.2k
Making Projects Easy
brettharned
117
6.3k
Fireside Chat
paigeccino
37
3.5k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
357
30k
How to train your dragon (web standard)
notwaldorf
96
6.1k
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