@@ -30,7 +30,7 @@ initialize. To begin writing revisions simply invoke `mgrt add`,
30
30
31
31
$ mgrt add "My first revision"
32
32
33
- this will create a new revision file in the ` migrations ` directory, and open
33
+ this will create a new revision file in the ` revisions ` directory, and open
34
34
it up for editting with the revision to write,
35
35
36
36
/*
@@ -84,15 +84,15 @@ code that was executed as part of that revision.
84
84
mgrt also offers the ability to sync the revisions that have been performed on
85
85
a database against what you have locally. This is achieved with ` mgrt sync ` , and
86
86
just like before, this also takes the ` -type ` and ` -dsn ` flags. Lets delete the
87
- ` migrations ` directory that was created for us and do a ` mgrt sync ` .
87
+ ` revisions ` directory that was created for us and do a ` mgrt sync ` .
88
88
89
- $ rm -rf migrations
89
+ $ rm -rf revisions
90
90
$ mgrt ls
91
91
$ mgrt sync -type sqlite3 -dsn acme.db
92
92
$ mgrt ls
93
93
20060102150405: Andrew Pillar <[email protected] > - My first revision
94
94
95
- with ` mgrt sync ` you can easily view the migrations that have been run against
95
+ with ` mgrt sync ` you can easily view the revisions that have been run against
96
96
different databases.
97
97
98
98
## Database connection
@@ -130,7 +130,7 @@ revision can only be performed once, and cannot be undone. If you wish to undo
130
130
a revision, then it is recommended to write another revision that does the
131
131
inverse of the prior.
132
132
133
- Revisions are stored in the ` migrations ` directory from where the ` mgrt add `
133
+ Revisions are stored in the ` revisions ` directory from where the ` mgrt add `
134
134
command was run. Each revision file is prefixed with a comment block header
135
135
that contains metadata about the revision itself, such as the ID, the author and
136
136
a short comment about the revision.
0 commit comments