In the Graphcool Framework, you can define the configuration of a Graphcool Service in the service definition
graphcool.yml and deploy it to a Graphcool Service using the Graphcool CLI.
A service definition consists of type definitions, permissions, functions and root tokens (formerly called permanent authentication tokens).
After an initial closed beta period, we are now ready to open up the Graphcool Framework Preview
Everyone is invited to test out the Framework, no further steps are required to get started!
npm remove -g graphcool npm install -g graphcool@next graphcool init graphcool # read usage information
- A collection of service definition examples for the new CLI workflow is maintained here: https://github.com/graphcool/graphcool.
- A collection of templates is maintained here: https://github.com/graphcool/templates. You can add templates for authentication, messaging and much more to your service definition and adjust them to suit your needs afterwards.
- Read the Framework docs (WIP): https://docs-next.graph.cool/reference/basics/cli-zboghez5go
Participation from the community in both repositories is highly appreciated.
Migrating Legacy Projects
Going forward, evolving a given project will only be possible from either the Console or the CLI.
New projects created with the CLI are automatically part of the new workflow and can only be changed via the CLI.
Existing projects and new projects created with the Console are considered to be legacy projects that can only be changed using the Console. Additionally, these projects can be migrated to the new workflow manually. After you migrate a legacy project, it can no longer be changed in the Console.
You have to join the beta program to be able to migrate a legacy project, please send me a PM with your email address for more information.
After a project has been migrated, you can download its configuration from the project settings.
Legacy projects with an active integration, or with a
PRE_WRITEfunction cannot be migrated to the Framework.
It’s not possible to reverse the migration of a legacy project.
Even after migrating a legacy project, you can still view and change its data using the Console. The Console’s databrowser and playground will continue to work for all projects.
The Framework will support workflows for multi-stage service deployments. More information about that soon!
All commands included in the usage information of the CLI are expected to work. If you experience something else or have a feature request, please let us know in the Framework repository on GitHub: https://github.com/graphcool/graphcool
Thanks a lot for your help with shaping the future of backend development