Database CI/CD and Schema Migration with MongoDB and GitHub

Estimated: 30 mins
Database CI/CD and Schema Migration with MongoDB and GitHub

A series of articles about Database CI/CD and Schema Migration with MongoDB

In the last article Database CI/CD and Schema Migration with MongoDB, you have tried UI workflow in Bytebase.

This tutorial will bring you to the next level by introducing the GitOps workflow, where you commit the schema change script to the GitHub repository, which will in turn trigger the schema deployment pipeline in Bytebase.

You can use Bytebase free version to finish the tutorial.

Features included

  • GitOps Workflow
  • Change History


Before you start this tutorial, make sure:

Step 1 - Run Bytebase in Docker and set the External URL generated by ngrok

ngrok is a reverse proxy tunnel, and in our case, we need it for a public network address in order to receive webhooks from VCS. ngrok we used here is for demonstration purposes. For production use, we recommend using Caddy.


  1. Run Bytebase in Docker with the following command:

    docker run --rm --init \
      --name bytebase \
      --publish 8080:8080 --pull always \
      --volume ~/.bytebase/data:/var/opt/bytebase \
  2. Bytebase is running successfully in Docker, and you can visit it via localhost:8080. Register an admin account and it will be granted the workspace admin role automatically.

  3. Login to ngrok Dashboard and complete the Getting Started steps to install and configure. If you want to use the same domain each time you launch ngrok, go to Cloud Edge > Domains, where you'll find the domain <<YOURS>> linked to your account.

  4. Run the ngrok command ngrok http --domain=<<YOURS>> 8080 to start ngrok with your specific domain, and you will see the output displayed below:


  5. Log in Bytebase and click the gear icon (Settings) on the top right. Click General under Workspace. Paste <<YOURS>> as External URL under Network section and click Update.


  6. Now you can access Bytebase via <<YOURS>>

Step 2 - Find your MongoDB instance in Bytebase

  1. Visit Bytebase Console through the browser via your ngrok URL. Log in using your account created from the previous tutorial. bb-login

  2. If you have followed the last article, you should have a project TestMongoDB and a database dbdemo.

Step 3 - Connect Bytebase with

  1. Click Settings on the top bar, and then click Workspace > GitOps. Choose and click Next. bb-gitops-github-step1

  2. Follow the instructions within STEP 2, and in this tutorial, we will use a personal account instead of an organization account. The configuration is similar.

  3. Go to your GitHub account. Click Settings on the dropdown menu. gh-settings-dropdown

  4. Click Developer Settings at the bottom of the left side bar. Click OAuth Apps, and click New OAuth App. gh-oauth-apps

  5. Fill Application name and then copy the Homepage and Authorization callback URL in Bytebase and fill them. Click Register application. gh-register-oauth

  6. After the OAuth application is created successfully. Click Generate a new client secret. Copy Client ID and this newly generated client secret and paste them back in Bytebase. gh-copy-client-id bb-gitops-github-step2 gh-auth

  7. Click Next. You will be redirected to the confirmation page. Click Confirm and add, and the Git provider is successfully added. bb-gitops-github-step3

Step 4 - Enable GitOps workflow with MongoDB

  1. Go to project TestMongoDB, click GitOps, and choose GitOps Workflow. Click Configure GitOps. bb-project-gitops-gitops-workflow

  2. Choose - the provider you just added. It will display all the repositories you can manipulate. Choose mongodb-test-bb-local. bb-project-gitops-github-repo

  3. Keep the default setting, and click Finish.

Step 5 - Change data for MongoDB by pushing SQL data change files to GitHub

  1. In your GitHub repository mongodb-test-bb-local, create a folder bytebase, then create a subfolder Test, and create an sql file following the pattern {{ENV_ID}}/{{DB_NAME}}##{{VERSION}}##{{TYPE}}##{{DESCRIPTION}}.sql. It is the default configuration for file path template setting under project GitOps.


    • test corresponds to {{ENV_ID}}
    • dbdemo corresponds to {{DB_NAME}}
    • 202303222200 corresponds to {{VERSION}}
    • dml corresponds to {{TYPE}}
    • insert_bella corresponds to {{DESCRIPTION}}

    Paste the sql script in it.

  id: 2,
  name: "Bella"


  1. Commit and push this file.

  2. Go to Bytebase, and go into project TestMongoDB. You’ll find there is a new Push Event and a new issue 106 created. bb-push-notification-only

  3. Click issue/106 and go the issue page. Click Resolve issue, and the issue will be Done. You’ll see

    • The issue is created via
    • The issue is executed without approval because it’s on Test environment where manual approval is skipped by default. The Assignee is Bytebase, because the execution is automatic, and requires no manual approval.
    • The SQL is exactly the one we have committed to the GitHub repository.
    • The Creator is A, because the GitHub user you use to commit the change has the same email address found in the Bytebase member list.


Summary and Next

Now you have tried out GitOps workflow, which will store your MongoDB data in GitHub and trigger the change upon committing the change to the repository, to bring your MongoDB change workflow to the next level of Database DevOps - Database as Code.

In real world scenario, you might have separate features and main branches corresponding to your dev and production environment, you can check out GitOps with Feature Branch Workflow to learn the setup. Have a try and look forward to your feedback!

Edit this page on GitHub

Subscribe to Newsletter

By subscribing, you agree with Bytebase's Terms of Service and Privacy Policy.