hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-14 17:02:49 +03:00
Code Issues Projects Releases Wiki Activity
751bd44fb7
graphql-engine/server/stack.yaml

54 lines
1.5 KiB
YAML
Raw Normal View History

move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
# For more information, see: http://docs.haskellstack.org/en/stable/yaml_configuration.html
# Specifies the GHC version and set of packages available (e.g., lts-3.5, nightly-2015-09-21, ghc-7.10.2)
# resolver: lts-10.8
optimise server startup time (close #1430) (#2120) 1. Reuses postgres connections during startup which reduces the overhead of opening and closing connections. 2. Faster schema cache building. This is done by fetching all the required data in a single sql statement.
2019-05-08 10:36:43 +03:00
resolver: lts-13.20
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
# Local packages, usually specified by relative directory name
packages:
- '.'
bump stackage to lts 13 and refer to hasura's pg-client-hs (#1747)
2019-03-14 17:55:33 +03:00
# - '../../../graphql-parser-hs'
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
# - extra-libs/aeson
# - extra-libs/logger/wai-logger
# Packages to be pulled from upstream that are not in the resolver (e.g., acme-missiles-0.3)
extra-deps:
bump stackage to lts 13 and refer to hasura's pg-client-hs (#1747)
2019-03-14 17:55:33 +03:00
- git: https://github.com/hasura/pg-client-hs.git
multiplexed subscriptions (#1934) * add types to represent unparsed http gql requests This will help when we add caching of frequently used ASTs * query plan caching * move livequery to execute * add multiplexed module * session variable can be customised depending on the context Previously the value was always "current_setting('hasura.user')" * get rid of typemap requirement in reusable plan * subscriptions are multiplexed when possible * use lazytx for introspection to avoid acquiring a pg connection * refactor to make execute a completely decoupled module * don't issue a transaction for a query * don't use current setting for explained sql * move postgres related types to a different module * validate variableValues on postgres before multiplexing subs * don't user current_setting for queries over ws * plan_cache is only visible when developer flag is enabled * introduce 'batch size' when multiplexing subscriptions * bump stackage to 13.16 * fix schema_stitching test case error code * store hashes instead of actual responses for subscriptions * internal api to dump subscriptions state * remove PlanCache from SchemaCacheRef * allow live query options to be configured on server startup * capture metrics for multiplexed subscriptions * more metrics captured for multiplexed subs * switch to tvar based hashmap for faster snapshotting * livequery modules do not expose internal details * fix typo in live query env vars * switch to hasura's pg-client-hs
2019-04-17 12:48:41 +03:00
commit: 85f9c2c15e4fa09f2e2a86dbb23149b5256bdd34
server: build now is multi-stage builds (fix #29) - Change the build flow to use docker multi-stage builds
2018-07-02 16:56:10 +03:00
- git: https://github.com/hasura/graphql-parser-hs.git
support allow-list for graphql queries (closes #989) (#2075)
2019-05-16 09:13:25 +03:00
commit: 39d175c5c7bca35ec04d13c92a39f600bd6413cf
bump stackage to lts 13 and refer to hasura's pg-client-hs (#1747)
2019-03-14 17:55:33 +03:00
- ginger-0.8.4.0
explain a graphql query, similar to explain of an sql statement (close #562) (#805)
2018-10-19 05:15:28 +03:00
bump stackage to lts 13 and refer to hasura's pg-client-hs (#1747)
2019-03-14 17:55:33 +03:00
# extra dep for pg-client-hs
sync metadata cache across multiple instances connected to same db (closes #1182) (#1574) 1. Haskel library `pg-client-hs` has been updated to expose a function that helps listen to `postgres` notifications over a `channel` in this [PR](https://github.com/hasura/pg-client-hs/pull/5) 2. The server records an event in a table `hdb_catalog.hdb_cache_update_event` whenever any `/v1/query` (that changes metadata) is requested. A trigger notifies a `cache update` event via `hasura_cache_update` channel 3. The server runs two concurrent threads namely `listener` and `processor`. The `listener` thread listens to events on `hasura_cache_update` channel and pushed into a `Queue`. The `processor` thread fetches events from that `Queue` and processes it. Thus server rebuilds schema cache from database and updates.
2019-03-12 08:46:27 +03:00
- select-0.4.0.1
bump stackage to lts 13 and refer to hasura's pg-client-hs (#1747)
2019-03-14 17:55:33 +03:00
- primitive-extras-0.7.1
- stm-hamt-1.2.0.2
optimise server startup time (close #1430) (#2120) 1. Reuses postgres connections during startup which reduces the overhead of opening and closing connections. 2. Faster schema cache building. This is done by fetching all the required data in a single sql statement.
2019-05-08 10:36:43 +03:00
- stm-containers-1.1.0.4
point jose version to 0.8.0.0 on github (closes #983) (#1202)
2018-12-14 07:21:29 +03:00
bump stackage to lts 13 and refer to hasura's pg-client-hs (#1747)
2019-03-14 17:55:33 +03:00
- reroute-0.5.0.0
- Spock-core-0.13.0.0
explain a graphql query, similar to explain of an sql statement (close #562) (#805)
2018-10-19 05:15:28 +03:00
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
# Override default flag values for local packages and extra-deps
flags: {}
# Extra package databases containing global packages
extra-package-dbs: []
# Control whether we use the GHC we find on the path
# system-ghc: true
# Require a specific version of stack, using version ranges
# require-stack-version: -any # Default
# require-stack-version: >= 1.0.0
# Override the architecture used by stack, especially useful on Windows
# arch: i386
# arch: x86_64
# Extra directories used by stack for building
# extra-include-dirs: [/path/to/dir]
# extra-lib-dirs: [/path/to/dir]
# Allow a newer minor version of GHC than the snapshot specifies
# compiler-check: newer-minor
Reference in New Issue Copy Permalink