Upgrade web UI packages
This commit is contained in:
16
README.md
16
README.md
@ -4,6 +4,8 @@
|
||||
|
||||
Get an high-performance GraphQL API for your Rails app in seconds. Super Graph will auto learn your database structure and relationships. Built in support for Rails authentication and JWT tokens.
|
||||
|
||||

|
||||
|
||||
## Back story and motivation
|
||||
|
||||
I have a Rails app that gets a bit of traffic. Having planned to improve the UI using React or Vue I found that my current APIs didn't have the data I needed and I was too lazy to build new endpoints. My controllers were esentially wrappers around database queries and I didn't enjoy having to figure out new REST APIs with paths, names and methods to fetch all this new data or write the active record code needed.
|
||||
@ -83,7 +85,16 @@ $ docker-compose -f docker-compose.image.yml up
|
||||
$ open http://localhost:8080
|
||||
```
|
||||
|
||||
The above command will download the latest docker image for Super Graph and use it to run an example that includes a Postgres DB and a simple Rails ecommerce store app. If you want to build and run Super Graph from code then use the following command instead `docker-compose up`
|
||||
The above command will download the latest docker image for Super Graph and use it to run an example that includes a Postgres DB and a simple Rails ecommerce store app.
|
||||
|
||||
If you want to build and run Super Graph from code then the below commands will build the web ui and launch Super Graph in developer mode with a water for code changes.
|
||||
|
||||
```console
|
||||
$ brew install yarn
|
||||
$ (cd web && yarn install && yarn build)
|
||||
$ go generate ./...
|
||||
$ docker-compose up
|
||||
```
|
||||
|
||||
#### How to try with an authenticated user
|
||||
|
||||
@ -173,9 +184,6 @@ query {
|
||||
}
|
||||
```
|
||||
|
||||
## Web UI for web developers
|
||||

|
||||
|
||||
## Configuration
|
||||
|
||||
Config files can either be in YAML or JSON their names are derived from the `GO_ENV` variable, for example `GO_ENV=prod` will cause the `prod.yaml` config file to be used. or `GO_ENV=dev` will use the `dev.yaml`. A path to the config files can be specified using the `-path <folder>` command line argument.
|
||||
|
Reference in New Issue
Block a user