e9ae080d28
### Description This small documentation PR explains why and how we use `ManagedT`, and how it solves problems we would have with `Managed`. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/8615 GitOrigin-RevId: 5b7710a8cb6373fefb69bb4e9e8eda389c14c2da
1.8 KiB
Server engineering documentation
This page documents the structure and the internal architecture of the GraphQL Engine Server. To get started, you can read the overview. We also maintain a glossary of all the terms we use throughout the code and the documentation.
You can also get started with a list of tips and tricks.
Haddock documentation
You can browse the engine's haddock documentation for the stable branch, main branch, and every previous version release since v2.2.0.
Architecture deep-dive
- how to understand our GraphQL schema
- how to perform database migrations
- how the execution of remote joins works
- how we manage resources
Backend-specific documentation
Notes
In our Haskell codebase, we use GHC-style
notes for long-form
comments detailing a specific aspect of the codebase. We gather all of them, as
of the main branch, in the notes subfolder.
Updating this documentation
All markdown files in this folder are either copied verbatim from
server/documentation
or generated as part of our CI; do not open a PR to modify files in
the gh-pages branch, and instead modify their source directly. Notes
are extracted using the scripts/extract-nodes bash script. The
haddock documentation is generated by running cabal haddock --haddock-internal --haddock-options="--ignore-all-exports".