Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin Cardano GraphQL to 0.1.6 #20

Merged
merged 1 commit into from Oct 3, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 2 additions & 4 deletions README.md
@@ -1,7 +1,7 @@
Cardano Explorer App
====================

Frontend web app for the Cardano Explorer. This project depends on the [Cardano GraphQL API Service](https://github.com/input-output-hk/cardano-graphql), as defined in the [docker stack](docker-compose.yml). The schema typings are generated from the running API service, and should be regenerated when changing the version.
Frontend web app for the Cardano Explorer. This project depends on the [Cardano GraphQL API stack](https://github.com/input-output-hk/cardano-graphql), as defined in [docker-compose](docker-compose.yml). The schema typings are generated from the running API service, and should be regenerated when changing the version.

## Development
### Start
Expand All @@ -15,9 +15,7 @@ By default the app will be at http://localhost:4000, and an instance of the Grap

The GraphQL API port can be customized with the GRAPHQL_PORT variable in .env.local. This value is respected by `yarn start-dependencies`.

`yarn start-dependencies` will pull the most recent development containers for cardano-graphql and the seed database. It will also regenerate the typings from any schema changes, which may lead to a git diff. This is to be expected and should be committed.

In the future, container versions will be statically pinned from the docker-compose.yml and only updated when appropriate to do so. For these early stages of development we want to ensure the backend and frontend remain aligned.
`yarn start-dependencies` will pull the Docker containers for the cardano-graphql stack, including the seeded PostgreSQL and Hasura instances. It will also regenerate the typings from any schema changes, which may lead to a git diff. This is to be expected and should be committed.

## Storybook

Expand Down
12 changes: 6 additions & 6 deletions docker-compose.yml
@@ -1,21 +1,21 @@
version: '3.7'
services:
api:
image: samjeston/cardano-graphql-dev:develop
image: samjeston/cardano-graphql-dev:0.1.6
restart: always
environment:
- HASURA_URI=http://hasura:8080/v1/graphql
ports:
- ${API_PORT:-3100}:3100
hasura:
image: hasura/graphql-engine:v1.0.0-beta.6
image: samjeston/cardano-graphql-hasura:0.1.6
depends_on:
- "postgres"
restart: always
environment:
HASURA_GRAPHQL_DATABASE_URL: postgres://nix:postgres@postgres:5432/cexplorer
HASURA_GRAPHQL_ENABLE_CONSOLE: "false"
HASURA_GRAPHQL_ENABLED_LOG_TYPES: startup
- HASURA_GRAPHQL_DATABASE_URL=postgres://nix:postgres@postgres:5432/cexplorer
- HASURA_GRAPHQL_ENABLE_CONSOLE=false
- HASURA_GRAPHQL_ENABLED_LOG_TYPES=startup
postgres:
image: samjeston/cardano-graphql-pgseed:develop
image: samjeston/cardano-graphql-pgseed:0.1.6
restart: always