Skip to content

Commit

Permalink
Standardize on database naming river_dev + river_test
Browse files Browse the repository at this point in the history
We have a whole bunch of ideas of what the name of the River test
database should be across like all our different projects. I'm going to
try and standardize on `river_test` everywhere, and `river_dev` for the
development database. Opened [1] over in the Ruby project.

[1] riverqueue/riverqueue-ruby#17
  • Loading branch information
brandur committed Jun 30, 2024
1 parent 25464be commit df9528d
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/development.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@ cp .env.example .env
```

```sh
$ createdb river-development
$ createdb river_dev
$ go install github.com/riverqueue/river/cmd/river
$ river migrate-up --database-url postgres://localhost/river-development
$ river migrate-up --database-url postgres://localhost/river_dev
```

## Go API
Expand All @@ -29,8 +29,8 @@ The API will need a build TypeScript UI in `ui/dist`, or you'll have to serve it
Raise test database:

```sh
$ createdb river-test
$ river migrate-up --database-url postgres://localhost/river-test
$ createdb river_test
$ river migrate-up --database-url postgres://localhost/river_test
```

Run tests:
Expand Down

0 comments on commit df9528d

Please sign in to comment.