Skip to content

Commit 266b66f

Browse files
committed
README: Common issues - Hasura
1 parent c8d9b0d commit 266b66f

File tree

1 file changed

+15
-2
lines changed

1 file changed

+15
-2
lines changed

README.md

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,9 @@ The all-in-one DataHack management platform, from registration to communications
44

55
## Running the development environment
66
1. Setup the project by running `./scripts/setup`
7-
2. Migrate the database schemas by running `./scripts/migration apply latest`
8-
3. If you want to populate the database then run `./scripts/backup restore lastest`
7+
2. boot containers `docker-compose up`
8+
3. Migrate the database schemas by running `./scripts/migration apply latest`
9+
4. If you want to populate the database then run `./scripts/backup restore lastest`
910

1011
> *Note:* if you want to populate the database from a different version/file run `./scripts/backup restore <file path>`
1112
@@ -34,6 +35,18 @@ In order to lint the project for code quality issues you could either run `./scr
3435
## Common Issues
3536

3637
- On macOS, if you get the error `realpath: command not found` then you should install coreutils which could be installed through brew by running `brew install coreutils`
38+
- Hasura fails to start. Run `docker-compose restart hasura`.
39+
40+
### hasura migration issues
41+
If step 3 (Migrate the database schemas by running `./scripts/migration apply latest`) fails. Try the following:
42+
- Make sure containers are up. `docker-compose up`
43+
- open a new terminal and run. `docker exec -it hasura sh`
44+
- go to hasura-migrations. `cd hasura-migrations`
45+
- Copy the last printed version number (e.g. 1582141486977).
46+
- Run `hasura-cli migrate apply --version 1582141486977`
47+
48+
You're all set.
49+
3750

3851
## Contributing
3952

0 commit comments

Comments
 (0)