-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
865 lines (802 loc) · 29.2 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>
Better dependency management: leverage composer to the limit.
</title>
<meta name="description" content="A talk about composer replacing drush make">
<meta name="author" content="Rodrigo Aguilera">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/solarized.css" id="theme">
<!-- Code syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<h1>
Better dependency management: leverage composer to the limit
</h1>
<h3>Can I use composer to do this?</h3>
<p>
<small>A talk by <a href="https://www.rodrigoaguilera.net">Rodrigo Aguilera</a> / <a href="https://twitter.com/marinero">@marinero</a></small>
</p>
<aside class="notes">
</aside>
</section>
<section>
<h2>Norok!</h2>
<p class="fragment">
<img src="ymbralogo.png" alt="Ymbra" width="250" style="border: 0; background-color: grey; padding: 2em;">
<br />
Focused on processes, workflows and shared tools
</p>
<aside class="notes">
Thanks to Moldovan asociation and sponsors.
I'm from Madrid, now I live in Barcelona. I work as a drupal developer at Ymbra, Citilab. <br />
Motivation: As I was moving to Drupal 8 I knew there was something better. <br />
I have a curiosity to improve process. <br>
I have been giving talks on default content, multilingual, behat, code review... <br />
</aside>
</section>
<section>
<h2>Agenda</h2>
<p>
<ul>
<li>The PHP reinassance</li>
<li>The old days of drush make and the Drupal island</li>
<li>Composer is awesome</li>
<li>Your drupal project has dependencies too</li>
<li>Compose all the things!</li>
</ul>
</p>
<aside class="notes">
No demos <br />
This an elastic talk I can give more weight to the beginning or the end.<br />
How many of you alredy build your projects with composer? <br />
</aside>
</section>
<section>
<section>
<h2>The PHP reinassance</h2>
<p><img src="images/phpelephant.jpg" alt="elephant"></p>
<p></p>
<aside class="notes">
Since 2014 we have seen PHP become a much more professional and clean language. <br>
</aside>
</section>
<section>
<h2>We had too much code</h2>
<p>
Took less time to write (or copypaste) a solution yourself than to find a component you can reuse.
</p>
<aside class="notes">
Is not such a bad idea but it wasn't getting PHP to be any good.
</aside>
</section>
<section>
<h2>Reusability</h2>
<p>Sharing must be easy or it won't happen.</p>
<p>Free software as a feature.</p>
<aside class="notes">
Free software as a practical feature comes into play because you see all this different projects sharing code.
</aside>
</section>
<section>
<h2>First attemps, aka: the way there</h2>
<p>
<ul>
<li>Pear (PHP 4, required root, lots of includes)</li>
<li>Class autoloading (PHP 5.0)</li>
<li>Github (As replacement of Sourceforge)</li>
<li>Namespaces (PHP 5.3)</li>
<li>PHP standards (PSR-x) from PHP-FIG</li>
</ul>
</p>
<aside class="notes">
Autoloading: how to search files with classes. <br />
Meanwhile in the Drupal island...
</aside>
</section>
</section>
<section>
<section>
<h2>The drupal island</h2>
<p>
<img src="images/drupal-diver.png" alt="Drupal diver" width="400">
</p>
<aside class="notes">
PHP is going to parties and drupal is not invited. <br />
Don't worry neither was wordpress or joomla.
</aside>
</section>
<section>
<h2>Drush make (2010)</h2>
<p>
<img src="images/drush.jpg" alt="">
</p>
<aside class="notes">
It wasn't part of drush and then it got merged into it. <br />
answers the problem about not having drupal and modules in repo.
</aside>
</section>
<section>
<h2>The shopping list</h2>
<p>
<pre><code>api = 2
core = 7.*
projects[views] = 3.1
projects[ctools] = 1.0-rc1
projects[media] = 2.x-dev
projects[nodequeue][subdir] = contrib
projects[nodequeue][version] = 2.0-alpha1
projects[nodequeue][patch][] = "http://drupal.org/files/issues/1023606-qid-to-name-6.patch"
projects[nodequeue][patch][] = "http://drupal.org/files/issues/nodequeue_d7_autocomplete-872444-6.patch"
libraries[jquery.cycle][download][type] = get
libraries[jquery.cycle][download][url] = http://malsup.com/jquery/cycle/release/jquery.cycle.zip?v2.99
libraries[jquery.cycle][destination] = libraries
</code></pre>
</p>
<aside class="notes">
Brings automation <br>
Allows patches, fixing version, external libraries, choice of folder, not all the code in the repository, can get from cvs. <br>
This in INI format, it also supports YAML.
</aside>
</section>
<section>
<h2>Problems</h2>
<p>
<ul>
<li>Downloads all the code everytime</li>
<li>All dependencies listed</li>
<li>You have to be specific about the versions</li>
<li>Only remote patches</li>
<li>Different make files for different purposes</li>
</ul>
</p>
<aside class="notes">
Some projects include a make file. <br>
One file for Drupal core, other for modules, libraries and themes, dev modules.
</aside>
</section>
</section>
<section>
<section>
<h2>Some brave sailors</h2>
<p>
<img src="images/sailor.png" alt="Drupal diver" width="400">
<img src="images/sailorwoman.jpg" alt="Sailorwoman" width="400">
</p>
<aside class="notes">
</aside>
</section>
<section>
<h2>Drupal makes some friends out there</h2>
<p>
Just by looking at the composer.json in drupal core
<ul>
<li>A lot of symfony components(dependency injection, events, routing, yaml, etc)</li>
<li>Twig</li>
<li>Guzzle</li>
<li>Composer</li>
<li>And much more</li>
</ul>
</p>
<aside class="notes">
Introduces symfony principles.
</aside>
</section>
</section>
<section>
<section>
<h2>Introducing Composer - 2012</h2>
<p>
<img src="images/composer.png" alt="Director" width="400">
</p>
<aside class="notes">
Is a fairly new tool, it has a history, is used by drupal core. <br />
Ugly logo. <br />
</aside>
</section>
<section>
<p>
<img src="images/composer-badass.png" alt="Director" width="400">
</p>
<aside class="notes">
Better logo. <br />
</aside>
</section>
<section>
<h2>The main goals</h2>
<p>
<ul>
<li><strong>Reuse </strong>third party libraries.</li>
<li><strong>Avoid </strong>dependency hell.</li>
<li><strong>Standarization</strong> among PHP projects</li>
</ul>
</p>
<aside class="notes">
It was decided to use components from other projects. <br />
Other PHP projects didn't had drush make.
</aside>
</section>
<section>
<h2>Definition</h2>
<p>
Composer is a tool for dependency management in PHP. It allows you to declare the dependent <strong>libraries </strong>your project needs and it will install them in your project for you.
</p>
<aside class="notes">
When we say libraries it can be other pieces of php code like themes, modules, or tools like behat.
</aside>
</section>
<section>
<h2>What it means</h2>
<p>
<ul>
<li class="fragment visible" data-fragment-index="0">No more Copy/Paste of libraries</li>
<li class="fragment visible" data-fragment-index="1">Resolves dependencies</li>
<li class="fragment visible" data-fragment-index="2">Each project defines its own requirements</li>
<li class="fragment visible" data-fragment-index="3">Performs build tasks</li>
<li class="fragment visible" data-fragment-index="4">Autoloading: all code under the same roof</li>
</ul>
</p>
<aside class="notes">
<ul>
<li>
Deps: You don't declare everything that is on your project. Only what you depend on.
</li>
<li>
Build: Downloading of js libraries, binaries, cleaning, scaffolding, tests
</li>
</ul>
</aside>
</section>
<section>
<h2>Similar to composer in diferent programming languages</h2>
<p>
<ul>
<li>npm (javascript)</li>
<li>pip (python)</li>
<li>rubygems (with bundler)</li>
</ul>
</p>
<aside class="notes">
<ul>
<li>Some are package managers and some are dependency managers or both</li>
</ul>
</aside>
</section>
<section>
<h2>Get Composer</h2>
<pre width="800"><code class="no-highlight" data-trim>
# Quick-n-easy:
$ curl -sS https://getcomposer.org/installer | php
# Global
$ curl -sS https://getcomposer.org/installer | php -- --install-dir=bin
</code></pre>
<aside class="notes">
This installs a binary.
</aside>
</section>
<section>
<h2>Structure of composer.json</h2>
<p>Base manifest file for your project</p>
<pre><code class="json" data-trim>
{
"name": "rodrigoaguilera/mydrupalsite",
"description": "This site is awesome.",
"require": {
"drupal/honeypot": "1.*"
},
"require-dev": {
"drupal/devel": "1.*"
},
"config": {},
"extra": {}
}
</code></pre>
<aside class="notes">
Is another shopping list but for higher level stuff. <br>
I just want Placinte and I don't care about the ingredients (Harbus as dessert)<br />
Devel modules are separated. <br />
There is other sections. <br />
</aside>
</section>
<section>
<h2>Composer.json and composer.lock</h2>
<p>
<ul>
<li>
The lock file has the dependencies already solved.<br>
</li>
<li>
The key to get everyone same versions is the lock file.
</li>
<li>
Always commit your lock file.
</li>
</ul>
</p>
<aside class="notes">
Everything downloaded with an exact version number. <br>
Lock is a bigger file. <br>
</aside>
</section>
<section>
<h2>Basic Commands</h2>
<aside class="notes">
There is more like "composer why" or why-not
</aside>
</section>
<section>
<h2>Install</h2>
<pre>
<code>
composer install
</code>
</pre>
<p>
Reads composer.lock and downloads all your dependencies in the /vendor directory.
</p>
<aside class="notes">
Everything gets a cache. <br>
Needed to develop drupal 8.1.x <br />
Options to use mostly on production environments. <br />
</aside>
</section>
<section>
<h2>Update</h2>
<pre>
<code>
composer update [<vendor>/<package>]
</code>
</pre>
<p>Writes a new composer.lock based on what is on composer.json and downloads only what is missing. <br>
You can update only one package to do more atomic updates.
</p>
<aside class="notes">
For last release crazies. <br />
A big project with lots of modules will update too much.
</aside>
</section>
<section>
<h2>Require</h2>
<p>
<pre>
<code>
composer require <vendor>/<package>:"<version-constrain>"
</code>
</pre>
</p>
<aside class="notes">
It will write your .json and .lock for you. <br />
semantic <br />
That is it. Three commands <br />
</aside>
</section>
<section>
<h2>Origin of libraries, modules, tools, etc.</h2>
<p>
The concept of repositories.
</p>
<aside class="notes">
</aside>
</section>
<section>
<h2>Packagist.org</h2>
<p>
Main repository for packages.<br>
There is also https://packages.drupal.org/8 as a mirror of the modules and themes on drupal.org
</p>
<aside class="notes">
It had an exponential growth.<br>
Declares what is stable. <br>
It manages outdated packages. <br>
The drupal community set up a repository before the official. <br />
</aside>
</section>
<section>
<h2>Execute binaries</h2>
<p>
<pre>
<code>
vendor/bin/drush
</code>
</pre>
</p>
<p>
<pre>
<code>
composer exec drush
</code>
</pre>
</p>
<aside class="notes">
Examples: drush, phpunit, phpcs, behat... <br>
Having this binaries in your PATH Is not an easy problem to solve for newbies. <br>
Drush solves it with drush launcher. <br />
</aside>
</section>
<section>
<h2>Global vs local</h2>
<p>
<ul>
<li>
The power of composer comes from having per project dependencies. <br>
</li>
<li>
But you can also install composer plugins or tools shared by all the projects in your machine. <br>
</li>
<li>
Use "composer global" before commands. (needs environment variable <code>$COMPOSER_HOME</code> to be set) <br>
</li>
</ul>
</p>
<aside class="notes">
Computer vs. only my repo. <br>
</aside>
</section>
<section>
<h2>Simulating environments</h2>
<p>
<pre>
<code class="json">
"config": {
"platform": {
"php": "5.6.2",
"ext-mongodb": "1.1"
}
}
</code>
</pre>
</p>
<aside class="notes">
Follow restrictions on install.
</aside>
</section>
<section>
<h2>Semantic versioning</h2>
<p>
<img src="images/semantic.png" alt="Versioning">
</p>
<aside class="notes">
All packagist supports this.<br>
A new feature of drupal 8. <br>
Contrib doesn't support it. <br />
</aside>
</section>
<section>
<h2>Composer in production</h2>
<p>
<pre>
<code>
composer install --prefer-dist --no-dev --optimize-autoloader
</code>
</pre>
<ul>
<li>No git repository files</li>
<li>The <code>require-dev</code> section is ignored</li>
<li>Faster autoloader</li>
</ul>
</p>
<aside class="notes">
</aside>
</section>
<section>
<h2>Component vs. project</h2>
<p>
The composer.json for a project (the root package) has more capabalities like:
<ul>
<li>Use your own repos</li>
<li>Define hook scripts (post-install, pre-update, etc.)</li>
<li>Configuration</li>
</ul>
</p>
<aside class="notes">
aka reusable library <br>
Root project depends on the context. <br />
you don't usually have to write it for a contrib module. <br />
</aside>
</section>
<section>
<h2>Patches</h2>
<p>
<pre>
<code class="json">
{
"require": {
"cweagans/composer-patches": "~1.0",
"drupal/drupal": "8.5.*@dev"
},
"config": {
"preferred-install": "source"
},
"extra": {
"patches": {
"drupal/drupal": {
"Add startup configuration for PHP server": "https://www.drupal.org/files/issues/add_a_startup-1543858-30.patch"
}
}
}
}
</code>
</pre>
</p>
<aside class="notes">
No command yet so it requires composer update <br />
If a library is heavily patched a fork is recommended. <br />
</aside>
</section>
<section>
<img src="images/quiz.gif" alt="Dawg" style="border: 0; width: 100%;">
<aside class="notes">
</aside>
</section>
<section>
<h2>Quiz: <code>install</code> or <code>update</code></h2>
<p>
<ul>
<li class="fragment" data-fragment-index="0">
Be sure you have the last updates from your team:
<code class="fragment" data-fragment-index="1">
composer install
</code>
</li>
<li class="fragment" data-fragment-index="2">
Deploying a new release of your application to production.
<code class="fragment" data-fragment-index="3">
composer install
</code>
</li>
<li class="fragment" data-fragment-index="4">
Checked out with git a new project and want to start coding.
<code class="fragment" data-fragment-index="5">
composer install
</code>
</li>
<li class="fragment" data-fragment-index="6">
Fetch new versions for the dependencies of your project.
<code class="fragment" data-fragment-index="7">
composer update
</code>
</li>
</ul>
</p>
<aside class="notes">
Only get new versions if you set your dependencies right.
</aside>
</section>
</section>
<section>
<section>
<h2>But... How do I use composer in my drupal project?</h2>
<p>
Composer template for drupal projects comes to the rescue. <br>
https://github.com/drupal-composer/drupal-project
</p>
<aside class="notes">
Is conceived as a replacement for drush make. <br />
People from pantheon, acquia are contributing. <br />
Proposes a structure for your project. <br />
</aside>
</section>
<section>
<h2>What does the template do?</h2>
<p>
<ul>
<li>Drupal will be downloaded with correct permissions ready for install.</li>
<li>Declaring a new depencency and downloading is one semantic command.</li>
<li>Modules, themes, and profiles (packages of type <code>drupal-[module|theme|profile]</code>) will be placed in <code>web/[module|theme|profile]/contrib/</code></li>
</ul>
</p>
<aside class="notes">
<ul>
<li>separates scaffold files from the real drupal core</li>
<li>Has a skeleton to put your drush aliases, config, tests</li>
<li>Once you clone it is yours</li>
</ul>
</aside>
</section>
<section>
<h2>What does the template do?</h2>
<p>
<ul>
<li>Creates default writable version of <code>settings.php</code>.</li>
<li>Latest version of drush is installed locally for use at <code>vendor/bin/drush</code>.</li>
<li>Latest version of DrupalConsole is installed locally for use at <code>vendor/bin/drupal</code>.</li>
</ul>
</p>
<aside class="notes">
<ul>
<li>The project is configured to use the generated composer autoloader instead of Drupal.</li>
</ul>
</aside>
</section>
<section>
<h2>Profit :D</h2>
<ul>
<li>Now everyone can have not only the same modules but also drush and console</li>
<li>Updating all your modules to the stable versions is just a couple of words away</li>
<li>Your continous integration system can become much more simple</li>
</ul>
<aside class="notes">
</aside>
</section>
</section>
<section>
<section>
<img src="images/compose-all.jpg" alt="Dawg" style="border: 0; width: 100%;">
<aside class="notes">
</aside>
</section>
<section>
<h2>Frontend libraries are also dependencies</h2>
<ul>
<li>Not in packagist (npmjs.org or bower)</li>
<li>Different locations than modules</li>
</ul>
<aside class="notes">
Any git repo can be a composer repo but is not practical for a lot of libraries. <br />
</aside>
</section>
<section>
<h2>asset-packagist.org</h2>
<ul>
<li>Add one repository to your root composer.json</li>
<li>Collects both packages from npm and bower under 2 vendors</li>
<li>Enables the ability to do <code>composer require npm-asset/bootstrap-sass:"^3"</code></li>
<li>Needs <code>oomphinc/composer-installers-extender</code> to define custom paths</li>
</ul>
<aside class="notes">
boostrap goes into custom theme but colorbox goes into libraries. <br />
Reduced the complexity of adding a third party library.
</aside>
</section>
<section>
<h2>Binary tools are also dependencies</h2>
<ul>
<li>Generally found in distribution's repositories (apt-get, yum, etc)</li>
<li>Usually compiled for a certain arquitecture and operating system</li>
<li>Specific packages for each binary</li>
<li>Available on vendor/bin/</li>
<li>Examples: mouf/nodejs-installer, jakoch/phantomjs-installer </li>
</ul>
<aside class="notes">
Phantomjs abandoned. <br />
</aside>
</section>
<section>
<img src="images/dawg-dependencies.jpg" alt="Dawg" style="border: 0; width: 100%;">
<aside class="notes">
Dependency on other depency managers like npm. <br />
</aside>
</section>
</section>
<section>
<section>
<h2>Recommendations</h2>
<aside class="notes">
</aside>
</section>
<section>
<h2>Minimum stability for all the dependencies or one by one</h2>
<p>For example:</p>
<pre>
"minimum-stability": "dev"
</pre>
<p>You can be more semantic and declare it for each package like</p>
<pre>
composer require "drupal/webform":"^5@beta",
</pre>
<aside class="notes">
There is an issue for this. <br />
</aside>
</section>
<section>
<h2>Config options</h2>
<pre><code class="json" data-trim>
"config": {
"sort-packages": true,
"discard-changes": true,
"process-timeout": 600,
"platform": {
"php": "7.1.0"
}
}
</code></pre>
<aside class="notes">
Avoid merge conflicts <br />
Since we use patches we need that from CI. <br />
Composer can take long especially on first run <br />
Depend on PHP version. <br />
</aside>
</section>
<section>
<h2>Vendoring</h2>
<p>Committing dependencies in the repo</p>
<img src="images/kittenkill.jpg" alt="Versioning">
<aside class="notes">
Not recommeded. Ongoing discussion. <br />
Neither composer nor git are deploy tools. <br />
</aside>
</section>
</section>
<section>
<section>
<h2>The future</h2>
<ul>
<li>Better user experience</li>
<li>Best practices</li>
<li>Make parts of Drupal reusable for other PHP projects</li>
</ul>
<aside class="notes">
Developers, site builders... <br />
I gave you some best practices few are standard. <br />
Commerce as an example that uses it extensibly. <br />
</aside>
</section>
</section>
<section>
<h2>Questions</h2>
<aside class="notes">
I didn't talk about operators for dependencies. <br />
Don't commit your vendor or your contrib <br />
</aside>
</section>
<section style="text-align: left;">
<h1>THE END</h1>
<p>
Multumesc. <br>
- <a href="https://getcomposer.org/">https://getcomposer.org/</a> <br>
</p>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
// Full list of configuration options available at:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
// Optional reveal.js plugins
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true },
{ src: 'plugin/notes/notes.js', async: true },
{ src: 'socket.io/socket.io.js', async: true },
{ src: 'plugin/notes-server/client.js', async: true }
]
});
Reveal.configure({
keyboard: {
13: 'next' // go to the next slide when the ENTER key is pressed
}
});
</script>
</body>
</html>