-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathexample-multiple.vmig.cnf
More file actions
executable file
·38 lines (31 loc) · 1.25 KB
/
example-multiple.vmig.cnf
File metadata and controls
executable file
·38 lines (31 loc) · 1.25 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
;; Vmig project configuration
;;
;; Put this file in your project root.
;; All path names are relative to the dirname of config
;; (absolute paths are allowed too).
;;
;; If you are using source control (svn, git, etc),
;; you need to make sure both schemes and migrations are versioned.
;;
;; MULTIPLE DATABASES MODE
;;
;; Vmig tracks multiple databases. Migrations and schemes will contain database names,
;; requiring you to have the same database names on all machines with the project.
;; List of tracked databases (separated by spaces)
databases=migrations
;; Name prefix to filter tables and other entities.
;; This way you can have multiple vmig projects in a single database.
name-prefix=
;; A table to store applied migrations. The table will be created if not exists;
;; database must exist.
migrations-table=migrations.migrations
;; A folder for your table schemes
schemes-path=database
;; A folder for your migrations
migrations-path=database/migrations
;; Mysql connection. If not set, default parameters are read from mysql console
;; client (essentially from ~/.my.cnf). You may review them by running
;; 'mysql --print-defaults'.
;connection=mysql://user:pass@host:port
;; Prevent any migration from running down (useful for production)
;fail-on-down=yes