Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,15 +76,15 @@ npm run start -- rinkeby

## Schema Migrations
Migrations are managed via knex and behave similarly to ActiveRecord
migrations. As you add migrations, knex tracks the currect applied state in the
migrations. As you add migrations, knex tracks the correct, current applied state in the
database, and allows you to apply new migrations as they come in.

See: [http://knexjs.org/#Migrations-CLI]

### Creating Migrations
New migrations are in typescript and are store in: ```src/migrations/```

To use the knex tool to generate a migration in this directly, use the *development* enironment:
To use the knex tool to generate a migration in this directly, use the *development* environment:

```
knex migrate:make -x ts --env development name
Expand All @@ -99,7 +99,7 @@ knex migrate:latest --env build

## Data Seeds
Seed files are used to seed the *test* database. Unlike migrations, seeds are
meant only for boostrapping, and so each time seeds are run all the source
meant only for bootstrapping, and so each time seeds are run all the source
files are executed (not just newly added ones). Currently the seeds files drop
and re-create the tables with each application.

Expand Down