-
Notifications
You must be signed in to change notification settings - Fork 7
Expand file tree
/
Copy pathdbmigration.html
More file actions
527 lines (461 loc) · 24.7 KB
/
dbmigration.html
File metadata and controls
527 lines (461 loc) · 24.7 KB
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
<!DOCTYPE html>
<html lang="en">
<head>
<title>Ebean ORM Setup</title>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<script async defer src="https://buttons.github.io/buttons.js"></script>
<link rel="shortcut icon" href="/images/favicon.ico" >
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css">
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.1.0/css/all.css" integrity="sha384-lKuwvrZot6UHsBSfcMvOkWwlCMgc0TaWr+30HWe3a4ltaBwTZhyTEggF5tJv8tbt" crossorigin="anonymous">
<link rel="stylesheet" href="/css/pygments.css" type="text/css" />
<link rel="stylesheet" href="/css/site.css">
</head>
<body>
<div id="wrap">
<div id="header">
<div class="navbar" role="navigation">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".mobile-nav">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="/">
<img src="/images/lg5-21x100.png" height="35">
</a>
</div>
<div class="collapse navbar-collapse">
<ul class="nav navbar-nav pull-right nav-btn-rhs">
<li ><a href="/"><span class="fas fa-home"></span> Home</a></li>
<li class="active"><a href="/docs">Docs</a></li>
<li ><a href="/docs/getting-started">Get Started</a></li>
<li ><a href="/support">Help</a></li>
<li ><a href="/videos">Videos</a></li>
<li ><a target="_blank" href="/apidoc/13">ApiDocs</a></li>
<li ><a href="/releases">Releases</a></li>
<li><a target="_blank" href="https://github.com/ebean-orm/ebean"> <i class="fab fa-github"></i></a></li>
</ul>
</div>
<div class="mobile-nav">
<ul class="nav navbar-nav pull-right nav-btn-rhs">
<li ><a href="/"><span class="fas fa-home"></span> Home</a></li>
<li class="active"><a href="/docs">Docs</a></li>
<li ><a href="/docs/getting-started">Get Started</a></li>
<li ><a href="/support">Help</a></li>
<li ><a href="/videos">Videos</a></li>
<li ><a target="_blank" href="/apidoc/13">ApiDocs</a></li>
<li ><a href="/releases">Releases</a></li>
<li><a target="_blank" href="https://github.com/ebean-orm/ebean"> <i class="fab fa-github"></i></a></li>
</ul>
</div>
</div>
</div>
</div>
<div id="main">
<div class="jumbotron mini">
<div class="container">
<h1><a href="/docs">Documentation</a> / <a href="/docs/setup">Setup</a> / DB Migration </h1>
</div>
</div>
<div class="container doc-index bs-docs-container">
<div class="row">
<div class="col-md-9" role="main">
<div class="bs-docs-section">
<h2 id="videos">Introduction</h2>
<div class="row">
<div class="col-md-6">
<div class="media ">
<div class="media-left">
<div class="media-left">
<a href="https://youtu.be/n7VXOFwM2og">
<img src="/images/movies-64.png" width="64" height="64" >
</a>
</div>
</div>
<div class="media-body">
<h4 class="media-heading">DB Migration introduction</h4>
Introduction to DB migration
</div>
</div>
</div>
<div class="col-md-6">
<div class="media ">
<div class="media-left">
<div class="media-left">
<a href="https://youtu.be/cxiacf0wmNk">
<img src="/images/movies-64.png" width="64" height="64" >
</a>
</div>
</div>
<div class="media-body">
<h4 class="media-heading">Repeatable migrations</h4>
Use of @View, extra-ddl.xml and repeatable migrations
</div>
</div>
</div>
</div>
<h2 id="overview">Overview</h2>
<p>
DB Migration is a feature for generation of DDL from the entity bean model that supports determining the
<code>diff</code> from the prior version of the model and generating appropriate DDL changes based on
the model difference.
</p>
<p>
You are expected to run the <code>diff</code> DDL using <code>FlywayDb</code>, <code>LiquiBase</code>
or similar tool. In the future Ebean will likely have built in support to run the DDL as it already has
most of the capability and could address some current issues with developer workflow and DDL script ordering.
</p>
<p>
DB migration has 2 output files:
</p>
<ul>
<li><b>Migration model XML</b> - This has the logical diff of the model as an <code>apply</code> or <code>pendingDrops</code> change set</li>
<li><b>Apply SQL</b> - This is the DDL script of the apply changes</li>
</ul>
<p>
When the DbMigration is run it loads any prior migration xml and combines that together
to define the prior model which is then compared against the existing entity beans.
</p>
<h4>Pending Drops</h4>
<p>
Only non-destructive changes are included in <code>apply</code> and changes like <code>drop table</code> and
<code>drop column</code> are put into a <code>pendingDrops</code> changeSet.
</p>
<p>
The drop pending changes need to be explicitly selected to go into a migration.
</p>
<p>
Given applications running in a clustered environment, pending drops typically need to trail the normal apply
changes by at least 1 migration. This delay could be minutes, days and some drops might not ever be run.
</p>
<h2 id="migration-xml">Migration xml</h2>
<p>
When DbMigration is run the <code>diff</code> to the model is determined and output
as the migration model xml document. This diff can have <code>apply</code> changes or <code>pendingDrops</code> changes.
</p>
<p>
From the migration <code>apply</code> changeSet the actual DDL that will be applied is generated.
</p>
<h4>Logical changes</h4>
<p>
Note that the changes
in the migration xml are database agnostic and a single migration xml document can be used
to generate migration DDL for multiple databases. For example, you can generate migration DDL
scripts for Postgres, Oracle and SQL Server from the single migration xml. In the migration xml
you will see logical types like JSON types (storing JSON documents in the DB) and for Postgres
that could translate to a JSONB and for Oracle to a CLOB.
</p>
<p>
The changes are also "logical" in the sense that changes to entities with @History and @Draftable
typically translates into multiple changes. For example adding a property to a @History entity could
add a column to the base table, add a column to the history table and a change the triggers as required.
</p>
<h4>Example migration xml</h4>
<p>
Below is an example migration xml generated with <code>apply</code> changes. The customer table
has 2 new columns added to it.
</p>
<p>
If the customer table has @History support this could also add columns to the history table and
update the associated db triggers.
</p>
<div class="syntax xml"><div class="highlight"><pre><span></span><span class="cp"><?xml version="1.0" encoding="UTF-8" standalone="yes"?></span>
<span class="nt"><migration</span> <span class="na">xmlns=</span><span class="s">"http://ebean-orm.github.io/xml/ns/dbmigration"</span><span class="nt">></span>
<span class="nt"><changeSet</span> <span class="na">type=</span><span class="s">"apply"</span><span class="nt">></span>
<span class="nt"><addColumn</span> <span class="na">tableName=</span><span class="s">"customer"</span><span class="nt">></span>
<span class="nt"><column</span> <span class="na">name=</span><span class="s">"registered"</span> <span class="na">type=</span><span class="s">"date"</span><span class="nt">/></span>
<span class="nt"><column</span> <span class="na">name=</span><span class="s">"comments"</span> <span class="na">type=</span><span class="s">"varchar(1000)"</span><span class="nt">/></span>
<span class="nt"></addColumn></span>
<span class="nt"></changeSet></span>
<span class="nt"></migration></span>
</pre></div>
</div>
<h4>Example migration with pendingDrops</h4>
<p>
Below is an example migration xml generated with <code>pendingDrops</code> changes.
</p>
<div class="syntax xml"><div class="highlight"><pre><span></span><span class="cp"><?xml version="1.0" encoding="UTF-8" standalone="yes"?></span>
<span class="nt"><migration</span> <span class="na">xmlns=</span><span class="s">"http://ebean-orm.github.io/xml/ns/dbmigration"</span><span class="nt">></span>
<span class="nt"><changeSet</span> <span class="na">type=</span><span class="s">"pendingDrops"</span><span class="nt">></span>
<span class="nt"><dropColumn</span> <span class="na">columnName=</span><span class="s">"shortTitle"</span> <span class="na">tableName=</span><span class="s">"document"</span> <span class="na">withHistory=</span><span class="s">"true"</span><span class="nt">/></span>
<span class="nt"></changeSet></span>
<span class="nt"></migration></span>
</pre></div>
</div>
<p>
Pending drop changes are not incorporated into the apply DDL script unless they are explicitly selected.
Once pending drops are applied they drop off the 'pending drops' list.
</p>
<h2 id="apply-ddl">Apply DDL</h2>
<p>
The apply ddl script contains the changes that we want to apply to the database.
This is the DDL script that you get FlywayDB or similar to run.
</p>
<h2>Applying pending drops</h2>
<div class="syntax text"><div class="highlight"><pre><span></span>INFO c.a.ebean.dbmigration.DbMigration - Pending un-applied drops in versions [1.2]
</pre></div>
</div>
<p>
The DB migration will log <code>INFO</code> level messages saying which migrations contain
pending drops that have not yet been applied. At some point it is decided to apply one of
the pending drops as the next migration.
</p>
<div class="syntax java"><div class="highlight"><pre><span></span><span class="c1">// generate a migration as the drops from migration version "1.2"</span>
<span class="n">System</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="s">"ddl.migration.pendingDropsFor"</span><span class="o">,</span> <span class="s">"1.2"</span><span class="o">);</span>
<span class="n">DbMigration</span> <span class="n">dbMigration</span> <span class="o">=</span> <span class="k">new</span> <span class="n">DbMigration</span><span class="o">();</span>
<span class="n">dbMigration</span><span class="o">.</span><span class="na">setPlatform</span><span class="o">(</span><span class="n">DbPlatformName</span><span class="o">.</span><span class="na">POSTGRES</span><span class="o">);</span>
<span class="n">dbMigration</span><span class="o">.</span><span class="na">generateMigration</span><span class="o">();</span>
</pre></div>
</div>
<p>
A migration is then generated with <code>dropsFor</code> set to the version of the migration that
had the pending drops that we want to apply. Additionally the migration apply ddl contains the
various drop statements that will be executed.
</p>
<div class="syntax xml"><div class="highlight"><pre><span></span><span class="cp"><?xml version="1.0" encoding="UTF-8" standalone="yes"?></span>
<span class="nt"><migration</span> <span class="na">xmlns=</span><span class="s">"http://ebean-orm.github.io/xml/ns/dbmigration"</span><span class="nt">></span>
<span class="nt"><changeSet</span> <span class="na">type=</span><span class="s">"apply"</span> <span class="na">dropsFor=</span><span class="s">"1.2"</span><span class="nt">></span>
<span class="nt"><dropColumn</span> <span class="na">columnName=</span><span class="s">"shortTitle"</span> <span class="na">tableName=</span><span class="s">"document"</span> <span class="na">withHistory=</span><span class="s">"true"</span><span class="nt">/></span>
<span class="nt"></changeSet></span>
<span class="nt"></migration></span>
</pre></div>
</div>
<h2 id="version-format">Version format</h2>
<p>
The "version" numbering format supported is the same as FlywayDB version numbering where you may use
"." or "_" (period or underscore) as separating characters.
</p>
<h5>Examples:</h5>
<p>
So <code>1.1</code> and <code>1_1</code> both translate as version <code>1.1</code>.
</p>
<p>
Note that version numbering controls the order in which migrations are executed and follows semantic
versioning so for example <code>1.1.1</code> would execute before <code>1.2</code>. By this means we
can add a "patch" migration.
</p>
<h3>Workflow</h3>
<p>
If you use Ebean's migration runner to execute the migration note that to run a migration the
<code>requirement is that the previous migration needs to have been run</code>. This is slightly
different from FlywayDB which requires either strict version number order (or we can disable that to
allow any ordering).
</p>
<p>
If you are using a workflow similar to "git flow" then Ebean's migration runner allows you to
process merge requests in a non-strict order. The assumption made for this to work is that in the case
where there are 2 or more merge requests (that are being reviewed and not yet merged into a common
DEV branch) will not have conflicting DB migration changes (If they do Ebean will allow the migration
to run but the migration itself will error).
</p>
<h2 id="version">Migration version and name</h2>
<p>
For a migration the developer needs to provide the <code>version</code> and <code>name</code>
and these can be set via environment variables, system properties or ebean.properties or programmatically.
</p>
<div class="syntax java"><div class="highlight"><pre><span></span><span class="n">System</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="s">"ddl.migration.version"</span><span class="o">,</span> <span class="s">"1.1"</span><span class="o">);</span>
<span class="n">System</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="s">"ddl.migration.name"</span><span class="o">,</span> <span class="s">"support end dating"</span><span class="o">);</span>
</pre></div>
</div>
<h2 id="on-startup">Generating migration on startup</h2>
<p>
The DB migration can be generated when the Ebean instance is started by setting <code>ddl.migration.generate</code>
system property or environment variable to true.
</p>
<div class="syntax java"><div class="highlight"><pre><span></span><span class="nd">@Test</span>
<span class="kd">public</span> <span class="kt">void</span> <span class="nf">generate</span><span class="o">()</span> <span class="o">{</span>
<span class="n">System</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="s">"ddl.migration.generate"</span><span class="o">,</span> <span class="s">"true"</span><span class="o">);</span>
<span class="n">System</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="s">"ddl.migration.version"</span><span class="o">,</span> <span class="s">"1.1"</span><span class="o">);</span>
<span class="n">System</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="s">"ddl.migration.name"</span><span class="o">,</span> <span class="s">"support end dating"</span><span class="o">);</span>
<span class="c1">// migration will be generated when Ebean starts</span>
<span class="c1">// ... typically by running your application.</span>
<span class="n">Database</span><span class="o">.</span><span class="na">builder</span><span class="o">().</span><span class="na">loadFromProperties</span><span class="o">().</span><span class="na">build</span><span class="o">();</span>
<span class="o">}</span>
</pre></div>
</div>
<h2 id="programmatic">Generate offline</h2>
<p>
We can generate a migration programmatically without starting your application.
In <code>src/test/java</code> add the following code with a <code>main method</code>.
</p>
<p>
Running this main method will generate the next migration and starts Ebean
in <code>offline mode</code>. This offline mode means we don't need to start the application
or need a database to generate the migration.
</p>
<div class="syntax java"><div class="highlight"><pre><span></span><span class="kn">package</span> <span class="nn">main</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">io.ebean.Platform</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">io.ebean.dbmigration.DbMigration</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">java.io.IOException</span><span class="o">;</span>
<span class="cm">/**</span>
<span class="cm"> * Generate the DB Migration.</span>
<span class="cm"> */</span>
<span class="kd">public</span> <span class="kd">class</span> <span class="nc">MainDbMigration</span> <span class="o">{</span>
<span class="cm">/**</span>
<span class="cm"> * Generate the next "DB schema DIFF" migration.</span>
<span class="cm"> * <p></span>
<span class="cm"> * These migration are typically run using FlywayDB, Liquibase</span>
<span class="cm"> * or Ebean's own built in migration runner.</span>
<span class="cm"> * </p></span>
<span class="cm"> */</span>
<span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="n">String</span><span class="o">[]</span> <span class="n">args</span><span class="o">)</span> <span class="kd">throws</span> <span class="n">IOException</span> <span class="o">{</span>
<span class="c1">// optionally specify the version and name</span>
<span class="c1">//System.setProperty("ddl.migration.version", "1.1");</span>
<span class="n">System</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="s">"ddl.migration.name"</span><span class="o">,</span> <span class="s">"support end dating"</span><span class="o">);</span>
<span class="c1">// generate a migration using drops from a prior version</span>
<span class="c1">//System.setProperty("ddl.migration.pendingDropsFor", "1.2");</span>
<span class="n">DbMigration</span> <span class="n">dbMigration</span> <span class="o">=</span> <span class="k">new</span> <span class="n">DbMigration</span><span class="o">();</span>
<span class="n">dbMigration</span><span class="o">.</span><span class="na">setPlatform</span><span class="o">(</span><span class="n">Platform</span><span class="o">.</span><span class="na">POSTGRES</span><span class="o">);</span>
<span class="c1">// generate the migration ddl and xml</span>
<span class="c1">// ... start in "offline" mode</span>
<span class="n">dbMigration</span><span class="o">.</span><span class="na">generateMigration</span><span class="o">();</span>
<span class="o">}</span>
<span class="o">}</span>
</pre></div>
</div>
<h2 id="running">Running migration</h2>
<p>
You can run the migrations using <code>FlywayDb</code>, <code>Liquibase</code> or Ebean's own
built in migration runner.
</p>
<h4>Ebean's migration runner</h4>
<div class="syntax properties"><div class="highlight"><pre><span></span><span class="c">## run migrations when the Ebean starts</span>
<span class="na">ebean.migration.run</span><span class="o">=</span><span class="s">true</span>
<span class="c">## optionally specify different DB credentials</span>
<span class="c">## to run the migration (own the tables)</span>
<span class="na">datasource.db.adminusername</span><span class="o">=</span><span class="s">myDbTableOwner</span>
<span class="na">datasource.db.adminpassword</span><span class="o">=</span><span class="s">secret</span>
</pre></div>
</div>
<p>
With <code>ebean.migration.run=true</code> then when the Ebean starts it will look at the
migrations and run any that need to be run. The migration runner will by default create a table
called <code>db_migration</code> that holds the meta data about the migrations that have been run
and inserts into this table when migrations are successfully executed.
</p>
<h2 id="repeatable">Repeatable migrations</h2>
<p>
Repeatable migrations are special migrations that start with <code>R__</code> and do not have a
version number. Repeatable migrations will run if they have not already been run or if there
content has changed (MD5 checksum has changed).
</p>
<p>
Repeatable migrations can contain any DDL but for ORM we use these for defining <code>database VIEWS</code>
and for example using <code>@View</code> for mapping entity beans to database views rather than tables.
</p>
<p>
Refer to the second video showing repeatable migrations with extra-ddl.xml and use with @View.
</p>
<div class="media ">
<div class="media-left">
<div class="media-left">
<a href="https://youtu.be/cxiacf0wmNk">
<img src="/images/movies-64.png" width="64" height="64" >
</a>
</div>
</div>
<div class="media-body">
<h4 class="media-heading">Repeatable migrations</h4>
Use of @View, extra-ddl.xml and repeatable migrations
</div>
</div>
<h4>FlywayDB note</h4>
<p>
For use with FlywayDB currently we need to prefix "version migrations" with <code>V</code> in order to
support both "version migrations" and "repeatable migrations". To do this:
</p>
<div class="syntax properties"><div class="highlight"><pre><span></span><span class="c">## must use V prefix on "version migrations" when using FlywayDB</span>
<span class="c">## with both "version" and "repeatable" migrations</span>
<span class="na">ebean.migration.applyPrefix</span><span class="o">=</span><span class="s">V</span>
</pre></div>
</div>
</div>
</div>
<div class="col-md-3" role="complementary">
<nav class="bs-docs-sidebar hidden-print hidden-xs hidden-sm">
<ul class="nav bs-docs-sidenav">
<li >
<a href="/docs/setup/enhancement">Enhancement</a>
</li>
<li >
<a href="/docs/setup/eclipse-apt">Eclipse IDE - APT</a>
</li>
<li >
<a href="/docs/setup/logging">Logging</a>
</li>
<li >
<a href="/docs/setup/serverconfig">DatabaseBuilder</a>
</li>
<li >
<a href="/docs/setup/guice">Guice</a>
</li>
<li >
<a href="/docs/setup/spring">Spring</a>
</li>
<li >
<a href="/docs/setup/activerecord">Active Record</a>
</li>
<li >
<a href="/docs/setup/ddl-create-all">DDL - Create All</a>
</li>
<li class="active">
<a href="/docs/setup/dbmigration">DDL - DB Migration</a>
<ul class="nav">
<li><a href="#introduction">Introduction</a></li>
<li><a href="#overview">Overview</a></li>
<li><a href="#migration-xml">Migration XML</a></li>
<li><a href="#apply-ddl">Apply DDL</a></li>
<li><a href="#version">Version and name</a></li>
<li><a href="#on-startup">Generate on startup</a></li>
<li><a href="#programmatic">Generate offline</a></li>
<li><a href="#running">Running migration</a></li>
<li><a href="#repeatable">Repeatable migrations</a></li>
</ul>
</li>
<li >
<a href="/docs/setup/test-properties"> Test properties</a>
</li>
<li >
<a href="/docs/setup/testing">Testing</a>
</li>
</ul>
</nav>
</div>
</div>
</div>
<!-- /.row -->
</div> <!-- /.container -->
</div>
</div>
<footer id="footer">
<div class="doc-footer">
<ul class="doc-footer-links">
<li><a href="/">Ebean ORM</a></li>
<li> | </li>
<li><a href="http://avaje-metric.github.io">Metrics</a></li>
</ul>
</div>
</footer>
<script type="text/javascript">
var categoryNames = {};
</script>
<script src="https://code.jquery.com/jquery-3.3.1.min.js"></script>
<script src="/js/bootstrap.min.js"></script>
<script src="/js/jquery.easing.min.js"></script>
<script src="/js/jquery.storageapi.min.js"></script>
<script src="/js/ebean-site.js"></script>
<script src="/js/extra.js"></script>
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-75181644-1', 'auto');
ga('send', 'pageview');
</script>
</body>
</html>