Moped Documentation
  • Welcome 👋
  • User Guides
    • Getting started
    • Map a project
  • Product Management
    • User communication
    • User management
    • User analytics
    • Local testing
    • Release process
    • Patch release process
    • MUI X Pro License
    • Integrations
      • Dataset documentation
      • ArcGIS Online
      • eCapris
      • Power BI
    • Features
  • Dev Guides
    • DB Docs & Data dictionary
    • Database backup policy
    • Moped Read Replica
    • How-to's
      • How do I start the Hasura cluster locally?
      • How do I launch the Hasura Console?
      • How do I get a JWT token?
      • How to ping the GraphQL API
      • How to ping the REST API
      • How do I connect a database with Postgres GUIs?
      • How do I connect to the RDS instance?
      • How to load production data into a local instance
      • How do I update seed data?
    • Hasura
      • Hasura Roles
      • Hasura Migrations
        • Getting Started
        • Installing the Hasura CLI
        • Configuration Files
        • Hasura Migration Principles
        • The Migration file format
        • Development
        • Hasura Seed Data
        • Running the Hasura Cluster Locally (video)
        • Create a migration: Exercise 1 (video)
        • Create a migration: Exercise 2 (video)
        • Latest hasura-cluster features
    • User Management
    • Authentication
      • Authentication Architecture
      • DynamoDB & Cognito
      • Secrets Manager & Cognito
      • Hasura & Cognito
      • React & Cognito
      • Flask API & Cognito
      • Single Sign-On with CTM
    • Code organization
    • API
      • Configuration Files
      • Testing
      • User Management API
    • Maps and geospatial data
      • Access tokens and API keys
      • Map libraries
      • Map data
      • Map styles
      • Map layers and basemaps
      • React patterns
      • V1 Archive
        • Map libraries
        • Map data
        • Map custom hooks
        • Map styles
        • Map layers and basemaps
    • UI access control
    • Design system
      • Branding
      • Component styles
      • Text content
    • Activity Log
      • Architecture
      • GitHub Actions and Deployment of Updates
      • Hasura Event Logs and Truncate Cron Job
      • Authentication
  • See also
  • Get Moped support, report a bug, or request an enhancement
  • Data & Technology Services
  • Github repository
Powered by GitBook
On this page
  • Introduction
  • Learning Curve

Was this helpful?

  1. Dev Guides
  2. Hasura
  3. Hasura Migrations

Getting Started

Why do we need Hasura CLI?

Introduction

The Hasura CLI plays a central role in database development. It allows you to:

  • Generate and execute database & hasura metadata migrations.

  • Run seed data operations

  • Run the Hasura Console (GraphiQL web client) cluster with different environments including prod, staging, local.

  • Reload metadata

  • Run API statements

  • And many more:

    • Create Hasura Actions

    • Make consistency checks

    • Install Hasura Plugins

    • Etc.

We will need it to implement best practices around the development of Moped, so unfortunately it is not an option to not use it. Luckily, there is ample support for multiple environments in Mac, Linux and Windows development.

Learning Curve

As with any serious production framework, there is a learning curve that will require some time to absorb the different components of a migration, and things might not make a lot of sense in the beginning. Fortunately, the migration system is simple compared to other frameworks and once we get used to it, it might in fact be an enjoyable feature of our workflow.

PreviousHasura MigrationsNextInstalling the Hasura CLI

Last updated 4 years ago

Was this helpful?