-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathfeatures.html
798 lines (681 loc) · 40.7 KB
/
features.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
<!DOCTYPE html>
<html lang="en">
<head>
<meta name="yandex-verification" content="00bf34bc7a08335d" />
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-137858449-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag() {
dataLayer.push(arguments);
}
gtag('js', new Date());
gtag('config', 'UA-137858449-1');
</script>
<!-- Yandex.Metrika counter -->
<script type="text/javascript">
(function (m, e, t, r, i, k, a) {
m[i] = m[i] || function () {
(m[i].a = m[i].a || []).push(arguments)
};
m[i].l = 1 * new Date();
k = e.createElement(t), a = e.getElementsByTagName(t)[0], k.async = 1, k.src = r, a.parentNode.insertBefore(k, a)
})
(window, document, "script", "https://mc.yandex.ru/metrika/tag.js", "ym");
ym(62712055, "init", {
clickmap: true,
trackLinks: true,
accurateTrackBounce: true,
webvisor: true
});
</script>
<noscript>
<div><img src="https://mc.yandex.ru/watch/62712055" style="position:absolute; left:-9999px;" alt="" /></div>
</noscript>
<!-- /Yandex.Metrika counter -->
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<meta
content="microservice configuration, configuration, cloud native, cloud native configuration, kubernetes, helm, configuration management, external configuration, configuration processor, configuration management tools, application configuration"
name="keywords">
<meta
content="Microconfig is a modern and simple way to manage microservice configuration. Especially in the Cloud."
name="description">
<link href="vendor/bootstrap/bootstrap.min.css" rel="stylesheet">
<link href="vendor/prism/prism.css" rel="stylesheet">
<link href="css/styles.css" rel="stylesheet">
<link href="bloggersans/bloggersans.css" rel="stylesheet">
<link rel="icon" href="css/favicon.ico">
<title>Microconfig.io - Microservice Configuration Made Easy</title>
</head>
<body>
<header>
<nav class="navbar navbar-expand-md navbar-light shadow-sm">
<div class="container">
<a href="./" class="navbar-brand">
<img style="height: 97px;" src="images/microconfig_logo_horizontal.svg" alt="Microconfig" />
</a>
<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarResponsive">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarResponsive">
<ul class="navbar-nav ml-auto">
<li class="nav-item nav-active">
<a class="nav-link text-dark" href="features.html">Features</a>
</li>
<li class="nav-item">
<a class="nav-link text-dark" href="quickstart.html">Quickstart</a>
</li>
<li class="nav-item">
<a class="nav-link text-dark" href="download.html">Download</a>
</li>
<li class="nav-item">
<a class="nav-link text-dark" href="plugin.html">IDE plugin</a>
</li>
<li class="nav-item">
<a class="nav-link text-dark" href="server.html">Server</a>
</li>
<li class="nav-item">
<a class="nav-link text-dark" href="documentation.html">Docs</a>
</li>
</ul>
</div>
</div>
</nav>
</header>
<a href="https://github.com/microconfig/microconfig" class="github-corner" aria-label="View source on GitHub">
<svg width="80" height="80" viewBox="0 0 250 250"
style="fill:#5fbb92; color:#fff; position: fixed; top: 0; border: 0; right: 0;z-index: 100"
aria-hidden="true">
<path d="M0,0 L115,115 L130,115 L142,142 L250,250 L250,0 Z"></path>
<path
d="M128.3,109.0 C113.8,99.7 119.0,89.6 119.0,89.6 C122.0,82.7 120.5,78.6 120.5,78.6 C119.2,72.0 123.4,76.3 123.4,76.3 C127.3,80.9 125.5,87.3 125.5,87.3 C122.9,97.6 130.6,101.9 134.4,103.2"
fill="currentColor" style="transform-origin: 130px 106px;" class="octo-arm"></path>
<path
d="M115.0,115.0 C114.9,115.1 118.7,116.5 119.8,115.4 L133.7,101.6 C136.9,99.2 139.9,98.4 142.2,98.6 C133.8,88.0 127.5,74.4 143.8,58.0 C148.5,53.4 154.0,51.2 159.7,51.0 C160.3,49.4 163.2,43.6 171.4,40.1 C171.4,40.1 176.1,42.5 178.8,56.2 C183.1,58.6 187.2,61.8 190.9,65.4 C194.5,69.0 197.7,73.2 200.1,77.6 C213.8,80.2 216.3,84.9 216.3,84.9 C212.7,93.1 206.9,96.0 205.4,96.6 C205.1,102.4 203.0,107.8 198.3,112.5 C181.9,128.9 168.3,122.5 157.7,114.1 C157.9,116.9 156.7,120.9 152.7,124.9 L141.0,136.5 C139.8,137.7 141.6,141.9 141.8,141.8 Z"
fill="currentColor" class="octo-body"></path>
</svg>
</a>
<main role="main" id="features">
<section class="jumbotron">
<div class="container">
<article class="markdown-body entry-content" itemprop="text">
<h1 class="text-center">Features</h1>
<p>This guide describes how Microconfig can help you solve common microservice configuration
problems.
</p>
<p>More details you can find in <a href="documentation.html">Docs</a>. </p>
<section id="layout">
<h2 class="mc-green section-title">Simple Configuration Layout</h2>
<div class="container">
<div class="row">
<div class="col-md-12 col-lg-6">
<h4>Problem</h4>
<p>Other configuration frameworks can demand a specific configuration folder
structure or specific filenames.
</p>
</div>
<div class="col-md-12 col-lg-6">
<h4>Solution</h4>
<p>Microconfig only asks you to create folders for your services somewhere in
<code>components</code> folder. You choose the names and folder structure. If
you have different types of configuration just place them in the same service
folder.
</p>
</div>
</div>
</div>
<pre><code class="language-shell">
components
├── payments
│ ├── payment-backend
│ │ ├── application.yaml
│ │ └── values.deploy
│ └── payment-frontend
│ ├── application.yaml
│ └── values.deploy
└── ...
...
</code></pre>
</section>
<section id="include">
<h2 class="mc-green section-title">Reuse Common Parts</h2>
<div class="container">
<div class="row">
<div class="col-md-12 col-lg-6">
<h4>Problem</h4>
<p>Microservices have a lot of shared configuration parts that is copy-pasted
between them. So you need to go through all services one by one to update this
shared part.
</p>
</div>
<div class="col-md-12 col-lg-6">
<h4>Solution</h4>
<p>Microconfig allows you to extract common parts of configuration to a dedicated
component and reuse it with <code>#include</code>. This way service config is
more focused on unique parts and all common parts are just included. In this
case if
you need to update your common part you just do it in one place and everyone
gets
this update via <code>#include</code>.
</p>
</div>
</div>
</div>
<div class="row-with-switch">
<label for="toggle-incl">Problem</label>
<input type="checkbox" id="toggle-incl" class="toggle" checked>
<label for="toggle-incl">Solution</label>
<div class="row equal-cols">
<div class="col-md-6 off">
<h3 class="code-title"><code>payment-backend</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-backend
server:
port: 8080
context: /api
monitoring:
secure: false
base-path: /monitoring
endpoints: info, health, ready, prometheus
logging:
level:
ROOT: INFO
APP: DEBUG
</code>
</pre>
</div>
<div class="col-md-6 off">
<h3 class="code-title"><code>payment-frontend</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-frontend
payment-backend:
host: http://payment-backend.local
path: /api
monitoring:
secure: true
base-path: /monitoring
endpoints: info, health, ready, prometheus
logging:
level:
ROOT: INFO
APP: DEBUG
</code>
</pre>
</div>
<div class="col-md-6 on">
<h3 class="code-title"><code>payment-backend</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-backend
server:
port: 8080
context: /api
#include monitoring, logging
</code>
</pre>
</div>
<div class="col-md-6 on">
<h3 class="code-title"><code>payment-frontend</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-frontend
payment-backend:
host: http://payment-backend.local
path: /api
#include monitoring, logging
monitoring:
secure: true
</code>
</pre>
</div>
</div>
<div class="row equal-cols">
<div class="col-md-6 on">
<h3 class="code-title"><code>monitoring</code></h3>
<pre class="code-block">
<code class="language-yaml">
monitoring:
secure: false
base-path: /monitoring
endpoints: info, health, ready, prometheus
</code>
</pre>
</div>
<div class="col-md-6 on">
<h3 class="code-title"><code>logging</code></h3>
<pre class="code-block">
<code class="language-yaml">
logging:
level:
ROOT: INFO
APP: DEBUG
</code>
</pre>
</div>
</div>
</div>
</section>
<section id="placeholders">
<h2 class="mc-green section-title">Reference Values</h2>
<div class="container">
<div class="row">
<div class="col-md-12 col-lg-6">
<h4>Problem</h4>
<p>Different services can depend on each other's configuration keys. For example
frontend needs backend's api base path. You can just keep this value in two
places but in this case you need to remember about this dependency and update
them
both.
</p>
</div>
<div class="col-md-12 col-lg-6">
<h4>Solution</h4>
<p>Microconfig can reference a value from current or another component with a
<code>${placeholder}</code>. This allows you to keep values only in original
services and all who depend on them can just have an explicit reference. In this
case you need to update the value only once.
</p>
</div>
</div>
</div>
<div class="row-with-switch">
<label for="toggle-ref">Problem</label>
<input type="checkbox" id="toggle-ref" class="toggle-mix-row" checked>
<label for="toggle-ref">Solution</label>
<div class="row equal-cols">
<div class="col-md-6 common">
<h3 class="code-title"><code>payment-backend</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-backend
server:
port: 8080
context: /api
...
</code>
</pre>
</div>
<div class="col-md-6 on">
<h3 class="code-title"><code>payment-frontend</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-frontend
payment-backend:
host: http://payment-backend.local
path: ${payment-backend@server.context}
...
</code>
</pre>
</div>
<div class="col-md-6 off">
<h3 class="code-title"><code>payment-frontend</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-frontend
payment-backend:
host: http://payment-backend.local
path: /api
...
</code>
</pre>
</div>
</div>
</div>
</section>
<section id="expressions">
<h2 class="mc-green section-title">Dynamic Values</h2>
<div class="container">
<div class="row">
<div class="col-md-12 col-lg-6">
<h4>Problem</h4>
<p>Sometimes static values are not enough, and you want to do a <code>+1</code> or
<code>base64</code>. Some values even are more readable as expressions. </p>
</div>
<div class="col-md-12 col-lg-6">
<h4>Solution</h4>
<p>Microconfig has <code>#{'expression' + 'language'} </code> to dynamically
generate your values. It supports math operations and much more. </p>
</div>
</div>
</div>
<div class="row-with-switch">
<label for="toggle-expr">Problem</label>
<input type="checkbox" id="toggle-expr" class="toggle" checked>
<label for="toggle-expr">Solution</label>
<div class="row equal-cols">
<div class="col-md-12 off">
<h3 class="code-title"><code>payment-frontend</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-frontend
payment-backend:
timeoutMs: 180000
log:
filename: PAYMENT-FRONTEND.log
...
</code>
</pre>
</div>
<div class="col-md-12 on">
<h3 class="code-title"><code>payment-frontend</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-frontend
payment-backend:
timeoutMs: #{ 3 * 60 * 1000 }
log:
filename: #{ '${this@name}'.toUpperCase() }.log
...
</code>
</pre>
</div>
</div>
</div>
</section>
<section id="env">
<h2 class="mc-green section-title">Environment Specific Config</h2>
<div class="container">
<div class="row">
<div class="col-md-12 col-lg-6">
<h4>Problem</h4>
<p>We deploy services to different environments that have specific properties. Your
production database has different ip address than your dev. All of those
specifications should be applied to final version for your environment.
</p>
</div>
<div class="col-md-12 col-lg-6">
<h4>Solution</h4>
<p>Microconfig supports specific values for each environment you need. You just
create an override <code>.env.</code> file near your base configuration. In this
file you specify all that you want for your <code>env</code> and it will be
merged
with your base configuration. More specific values will override base ones.
</p>
</div>
</div>
</div>
<div class="row-with-switch">
<label for="toggle-env">Problem</label>
<input type="checkbox" id="toggle-env" class="toggle" checked>
<label for="toggle-env">Solution</label>
<div class="row equal-cols">
<div class="col-md-6 off">
<h3 class="code-title"><code>payment-backend dev</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-backend
payment-gateway: http://gateway-mock.local
database:
type: Postgres
pool-size: 10
url: jdbc:postgres://10.10.10.10:5432/database
...
</code>
</pre>
</div>
<div class="col-md-6 off">
<h3 class="code-title"><code>payment-backend prod</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-backend
payment-gateway: https://payment-gateway.com
database:
type: Postgres
pool-size: 50
url: jdbc:postgres://20.20.20.20:5432/database
...
</code>
</pre>
</div>
<div class="col-md-6 on">
<h3 class="code-title"><code>payment-backend/application.dev.yaml</code></h3>
<pre class="code-block">
<code class="language-yaml">
payment-gateway: http://gateway-mock.local
database:
host: 10.10.10.10
</code>
</pre>
</div>
<div class="col-md-6 on">
<h3 class="code-title"><code>payment-backend/application.prod.yaml</code></h3>
<pre class="code-block">
<code class="language-yaml">
payment-gateway: https://payment-gateway.com
database:
host: 20.20.20.20
pool-size: 50
</code>
</pre>
</div>
</div>
<div class="row equal-cols">
<div class="col-md-12 col-lg-6 offset-lg-3 on">
<h3 class="code-title"><code>payment-backend/application.yaml</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-backend
database:
type: Postgres
pool-size: 10
url: jdbc:postgres://${this@database.host}:5432/database
</code>
</pre>
</div>
</div>
</div>
</section>
<section id="templates">
<h2 class="mc-green section-title">Static Files Templating</h2>
<div class="container">
<div class="row">
<div class="col-md-12 col-lg-6">
<h4>Problem</h4>
<p>Your services usually require some additional 3rd party configuration files like
a log configuration or a deploy script. It's easy if these files don't have
difference for every service but what if you need to change them a bit for each
service or environment?
</p>
</div>
<div class="col-md-12 col-lg-6">
<h4>Solution</h4>
<p>Microconfig can use static templates and populate them with data unique for each
service via placeholders and <a
href="https://mustache.github.io/">Moustache</a>. So you can
keep your template in one place and then generate specific result for each
service.
</p>
</div>
</div>
</div>
<div class="row-with-switch">
<label for="toggle-tmpl">Problem</label>
<input type="checkbox" id="toggle-tmpl" class="toggle" checked>
<label for="toggle-tmpl">Solution</label>
<div class="row equal-cols">
<div class="col-md-6 off">
<h3 class="code-title"><code>payment-backend log config dev</code></h3>
<pre class="code-block">
<code class="lang-xml">
<configuration>
<appender class="FileAppender">
<file>logs/payment-backend.log</file>
<encoder>
<pattern>%d{HH:mm:ss} %-5level %logger %msg %n</pattern>
</encoder>
</appender>
</configuration>
</code>
</pre>
</div>
<div class="col-md-6 off">
<h3 class="code-title"><code>payment-backend log config prod</code></h3>
<pre class="code-block">
<code class="lang-xml">
<configuration>
<appender class="FileAppender">
<file>logs/payment-backend.log</file>
<encoder>
<pattern>%d{HH:mm:ss} %-5level %logger %msg %n</pattern>
</encoder>
</appender>
<appender class="LogstashTcpSocketAppender">
<destination>30.30.30.30:9600</destination>
<encoder class="LogstashEncoder">
<customFields>{"servicename":"payment-backend"}</customFields>
</encoder>
</appender>
</configuration>
</code>
</pre>
</div>
<div class="col-md-6 on">
<h3 class="code-title"><code>log template.xml</code></h3>
<pre class="code-block">
<code class="language-xml">
<configuration>
<appender class="FileAppender">
<file>logs/${this@name}.log</file>
<encoder>
<pattern>%d{HH:mm:ss} %-5level %logger %msg %n</pattern>
</encoder>
</appender>
{{#appender.stash}}
<appender class="LogstashTcpSocketAppender">
<destination>30.30.30.30:9600</destination>
<encoder class="LogstashEncoder">
<customFields>{"servicename":"${this@name}"}</customFields>
</encoder>
</appender>
{{/appender.stash}}
</configuration>
</code>
</pre>
</div>
<div class="col-md-6 on">
<h3 class="code-title"><code>payment-backend prod</code></h3>
<pre class="code-block">
<code class="language-yaml">
mc.mustache.log:
fromFile: ${log@configDir}/template.xml
toFile: logback.xml
name: payment-backend
#var appender.stash: true
...
</code>
</pre>
</div>
</div>
</div>
</section>
<section id="diff">
<h2 class="mc-green section-title">Config Diff</h2>
<div class="container">
<div class="row">
<div class="col-md-12 col-lg-6">
<h4>Problem</h4>
<p>When you have your configuration in some kind of templating engine it might be
difficult to keep track of changes or compare different versions of
configuration.
For example, before new deployment to production you want to know what has been changed
in your configuration.
</p>
</div>
<div class="col-md-12 col-lg-6">
<h4>Solution</h4>
<p>Microconfig allows you to generate git style <code>diff</code> and see how your
configuration changes overtime or compare different versions.</p>
</div>
</div>
</div>
<div class="row-with-switch">
<label for="toggle-diff">Problem</label>
<input type="checkbox" id="toggle-diff" class="toggle" checked>
<label for="toggle-diff">Solution</label>
<div class="row equal-cols">
<div class="col-md-6 common">
<h3 class="code-title"><code>payment-frontend v1</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-frontend
monitoring:
base-path: /monitoring
endpoints: info, health, ready, prometheus
payment-backend:
host: http://payment-backend.local
path: /api
server:
maxThreads: 100
minThreads: 10
port: 80
timeoutMs: 180000
</code>
</pre>
</div>
<div class="col-md-6 common">
<h3 class="code-title"><code>payment-frontend v2</code></h3>
<pre class="code-block">
<code class="language-yaml">
name: payment-frontend
monitoring:
base-path: /monitoring
endpoints: info, health, ready, prometheus
payment-backend:
host: https://payment-backend.local
path: /api
timeoutMs: 180000
server:
port: 80
</code>
</pre>
</div>
</div>
<div class="row equal-cols">
<div class="col-md-12 col-lg-6 offset-lg-3 on">
<h3 class="code-title"><code>payment-frontend diff between v1 and v2</code></h3>
<pre class="code-block">
<code class="language-yaml">
+payment-backend:
timeoutMs: 180000
-server:
maxThreads: 100
minThreads: 10
timeoutMs: 180000
payment-backend:
host: http://payment-backend.local -> https://payment-backend.local
</code>
</pre>
</div>
</div>
</div>
</section>
<p class="text-dark">Can't wait to try it out? Head over to <a href="quickstart.html">Quickstart</a>
</p>
</article>
</div>
</section>
</main>
<footer class="text-muted bg-light">
<div class="container footer-container">
<p class="copyright">Microconfig.io ©</p>
<div class="contacts">
<ul class="list-unstyled mb-0">
<li class="lead">Join our
<a
href="https://join.slack.com/t/microconfig/shared_invite/zt-dflf2m0n-wOPVfAmk5eiHPn_9Omff7Q">Slack!</a>
</li>
<li class="lead">Contribute on <a href="https://github.com/microconfig/microconfig">Github</a></li>
<li class="lead"><a href="mailto:hello@microconfig.io">hello@microconfig.io</a></li>
</ul>
</div>
</div>
</footer>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js"></script>
<script src="vendor/bootstrap/bootstrap.bundle.min.js"></script>
<script src="vendor/prism/prism.js"></script>
<script async src="script/setCodeBlockHeight.js"></script>
</body>
</html>