mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-19 13:31:43 +03:00
66a3ad4d36
This PR was migrated from https://github.com/hasura/graphql-engine/pull/6254 --- > ### Description > ### Changelog - [ ] `CHANGELOG.md` is updated with user-facing content relevant to this PR. If no changelog is required, then add the `no-changelog-required` label. ### Affected components - [ ] Server - [ ] Console - [ ] CLI - [ ] Docs - [ ] Community Content - [ ] Build System - [ ] Tests - [ ] Other (list it) ### Related Issues -> ### Solution and Design > ### Steps to test and verify > ### Limitations, known bugs & workarounds > ### Server checklist #### Catalog upgrade Does this PR change Hasura Catalog version? - [ ] No - [ ] Yes - [ ] Updated docs with SQL for downgrading the catalog #### Metadata Does this PR add a new Metadata feature? - [ ] No - [ ] Yes - Does `run_sql` auto manages the new metadata through schema diffing? - [ ] Yes - [ ] Not required - Does `run_sql` auto manages the definitions of metadata on renaming? - [ ] Yes - [ ] Not required - Does `export_metadata`/`replace_metadata` supports the new metadata added? - [ ] Yes - [ ] Not required #### GraphQL - [ ] No new GraphQL schema is generated - [ ] New GraphQL schema is being generated: - [ ] New types and typenames are correlated #### Breaking changes - [ ] No Breaking changes - [ ] There are breaking changes: 1. Metadata API Existing `query` types: - [ ] Modify `args` payload which is not backward compatible - [ ] Behavioural change of the API - [ ] Change in response `JSON` schema - [ ] Change in error code 2. GraphQL API Schema Generation: - [ ] Change in any `NamedType` - [ ] Change in table field names Schema Resolve:- - [ ] Change in treatment of `null` value for any input fields 3. Logging - [ ] Log `JSON` schema has changed - [ ] Log `type` names have changed Co-authored-by: Thomas Güttler <414336+guettli@users.noreply.github.com> GitOrigin-RevId: 8381a182e9f380b98e0ebe918727e0ccae103e14
65 lines
1.5 KiB
ReStructuredText
65 lines
1.5 KiB
ReStructuredText
.. meta::
|
|
:description: Managing teams in Hasura Cloud
|
|
:keywords: hasura, docs, cloud, teams
|
|
|
|
.. _projects:
|
|
|
|
Projects & collaborators
|
|
========================
|
|
|
|
.. contents:: Table of contents
|
|
:backlinks: none
|
|
:depth: 1
|
|
:local:
|
|
|
|
Introduction
|
|
------------
|
|
|
|
The ``Projects`` page shows a list of your projects.
|
|
|
|
.. thumbnail:: /img/graphql/cloud/projects/projects-list.png
|
|
:alt: Projects list
|
|
:width: 1200px
|
|
|
|
For each project, you can do the one of the following actions:
|
|
|
|
.. thumbnail:: /img/graphql/cloud/projects/project-actions.png
|
|
:alt: Project actions
|
|
:width: 860px
|
|
|
|
- Click ``Launch Console`` to open the Hasura console in your browser. The ``Pro`` tab
|
|
lets you use the Pro features that Hasura Cloud has set up for you.
|
|
|
|
.. thumbnail:: /img/graphql/cloud/metrics/pro-tab-overview.png
|
|
:alt: Hasura Console: Pro tab
|
|
:width: 900px
|
|
|
|
- Click the gear icon to manage your project
|
|
|
|
.. thumbnail:: /img/graphql/cloud/projects/project-details.png
|
|
:alt: General tab
|
|
:width: 900px
|
|
|
|
.. note::
|
|
|
|
Please see the :ref:`API reference <cloud_api_reference>` to create and manage Hasura Cloud projects programmatically.
|
|
|
|
Dig deeper
|
|
----------
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
:titlesonly:
|
|
|
|
Creating projects <create>
|
|
Project Details <details>
|
|
Project Collaborators <collaborators>
|
|
Project Env vars <env-vars>
|
|
Project Domains <domains>
|
|
Securing projects <secure>
|
|
Switching pricing plans <pricing>
|
|
Deployment regions <regions>
|
|
Heroku database URL Sync <heroku-url-sync>
|
|
Deleting projects <delete>
|
|
|