You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,9 @@ The all-in-one DataHack management platform, from registration to communications
4
4
5
5
## Running the development environment
6
6
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`
9
10
10
11
> *Note:* if you want to populate the database from a different version/file run `./scripts/backup restore <file path>`
11
12
@@ -34,6 +35,18 @@ In order to lint the project for code quality issues you could either run `./scr
34
35
## Common Issues
35
36
36
37
- 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`
0 commit comments