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
160
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
79
Deploy your application in a box - 010PHP
wjzijderveld
0
160
Let's write some history - PHPDay 2016
wjzijderveld
1
200
Let's write some History - PHPBenelux 2016
wjzijderveld
1
220
Event Sourcing in practice @ Qandidate.com
wjzijderveld
1
320
Let's write some history - DPC 2015
wjzijderveld
1
210
Symfony CMF - A Decoupled Content Management Framework
wjzijderveld
0
94
PHPCR: A (better) way to structure content
wjzijderveld
0
120
Other Decks in Programming
See All in Programming
GraphQL あるいは React における自律的なデータ取得について
quramy
11
3k
サーバーレスで負荷試験!Step Functions + Lambdaを使ったk6の分散実行
shuntakahashi
6
1.6k
The Shape of a Service Object
inem
0
520
Why Prism?
kddnewton
4
1.7k
[DroidKaigi 2024] Android ViewからJetpack Composeへ 〜Jetpack Compose移行のすゝめ〜 / From Android View to Jetpack Compose: A Guide to Migration
syarihu
1
630
状態管理ライブラリZustandの導入から運用まで
k1tikurisu
3
470
全部見せます! クラシルリワードのSwiftTesting移行プロジェクト
uetyo
0
210
Pythonで改めて考える「クラス(class)」の使いどころ
os1ma
1
240
GenU導入でCDKに初挑戦し、悪戦苦闘した話
hideg
0
160
Ruby Parser progress report 2024
yui_knk
2
230
Go1.23で入った errorsパッケージの小さなアプデ
kuro_kurorrr
2
390
Kotlin 2.0 and Beyond
antonarhipov
2
150
Featured
See All Featured
The Mythical Team-Month
searls
218
43k
Fashionably flexible responsive web design (full day workshop)
malarkey
401
65k
Scaling GitHub
holman
458
140k
Optimising Largest Contentful Paint
csswizardry
30
2.8k
jQuery: Nuts, Bolts and Bling
dougneiner
61
7.4k
Rebuilding a faster, lazier Slack
samanthasiow
78
8.6k
The Art of Programming - Codeland 2020
erikaheidi
48
13k
Thoughts on Productivity
jonyablonski
66
4.2k
For a Future-Friendly Web
brad_frost
174
9.3k
How To Stay Up To Date on Web Technology
chriscoyier
786
250k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
123
18k
Designing on Purpose - Digital PM Summit 2013
jponch
114
6.8k
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