Elgato_dark/console
1
0
Fork 0
mirror of https://github.com/graphql-hive/console synced 2026-04-21 14:37:17 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Fix typo (#3233)

Browse source
This commit is contained in:
VaibhavWakde52 2023-10-31 22:40:03 +05:30 committed by GitHub
parent 76b52049c2
commit 0e81d9f6d3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -15,7 +15,7 @@ GraphQL Hive has been built with 3 main objectives in mind:
- **Help GraphQL developers to get to know their GraphQL APIs** a little more with our Schema
Registry, Performance Monitoring, Alerts, and Integrations.
- **Support all kinds of GraphQL APIs**, from Federation, and Stitching, to standalone APIs.
- **Open Source at the heart**: 100% open-source and build in public with the community.
- **Open Source at the heart**: 100% open-source and built in public with the community.
- **A plug and play Cloud solution**: to give access to Hive to most people with a generous free
"Hobby plan"
@ -45,7 +45,7 @@ your own infrastructure.
GraphQL Hive helps you get a global overview of the usage of your GraphQL API with:
- Error rates and repartition
- Global and queries performances (latency, RPM…)
- Global and query performances (latency, RPM…)
- Operations count
- Active GraphQL clients
@ -57,7 +57,7 @@ as smoothly as possible!
GraphQL Hive can notify your team when schema changes occur, either via Slack or a custom webhook.
Also, the Hive CLI allows integration of the schema checks mechanism to all CI/CD systems (GitHub,
BitBucket, Azure, and others). The same applies for schema publishing and operations checks.
BitBucket, Azure, and others). The same applies to schema publishing and operations checks.
If you are using GitHub, you can directly benefit from the **GraphQL Hive app that will
automatically add status checks to your PRs**!

6
docs/DEPLOYMENT.md
View file

@ -1,7 +1,7 @@
## Deployment
Deployment is based on NPM packages. That means we are bundling (as much as possible) each service
or package, and publish it to the private GitHub Packages artifactory.
or package, and publish it to the private GitHub Packages Artifactory.
Doing that allows us to have a simple, super fast deployments, because we don't need to deal with
Docker images (which are heavy).
@ -19,5 +19,5 @@ pricing, cold start and so on).
We are using Pulumi (infrastructure as code) to describe and run our deployment. It's managed as
GitHub Actions that runs on every bump release by Changesets.
So changes are aggregated in a Changesets PR, and when merge, it updated the deployment manifest
`package.json`, leading to a deployment of only the updated packages to production.
So changes are aggregated in a Changesets PR, and when merged, it updates the deployment manifest
`package.json`, leading to deployment of only the updated packages to production.