Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions mintlify/change-database/change-workflow.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -105,31 +105,31 @@ Bytebase offers two workflows to integrate with your existing processes:

### Choose UI-Driven Workflow If:

**You prefer visual interfaces** — Point-and-click change management with immediate feedback
- **You prefer visual interfaces** — Point-and-click change management with immediate feedback

**You need centralized control** — All database changes managed in one dedicated platform
- **You need centralized control** — All database changes managed in one dedicated platform

**Multiple teams involved** — DBAs, security, and compliance teams need visibility and approval rights
- **Multiple teams involved** — DBAs, security, and compliance teams need visibility and approval rights

**No existing CI/CD for databases** — Get started quickly without setting up additional infrastructure
- **No existing CI/CD for databases** — Get started quickly without setting up additional infrastructure

**Ad-hoc changes are common** — Hotfixes and emergency changes need quick turnaround
- **Ad-hoc changes are common** — Hotfixes and emergency changes need quick turnaround

**Best for:** Teams establishing database DevOps practices, organizations with dedicated DBAs, enterprises requiring multi-level approvals

[Learn more about UI-Driven Workflow →](/change-database/plan)

### Choose GitOps Workflow If:

**Database schema = Application code** — Migration scripts live alongside your application
- **Database schema = Application code** — Migration scripts live alongside your application

**Existing CI/CD pipelines** — Database changes follow your established deployment process
- **Existing CI/CD pipelines** — Database changes follow your established deployment process

**Developer-centric culture** — Engineers own the full stack including database
- **Developer-centric culture** — Engineers own the full stack including database

**Git is your source of truth** — All changes tracked through version control
- **Git is your source of truth** — All changes tracked through version control

**Automation first** — Minimize manual intervention in deployments
- **Automation first** — Minimize manual intervention in deployments

**Best for:** DevOps teams, microservices architectures, organizations practicing Infrastructure-as-Code

Expand All @@ -143,4 +143,4 @@ Bytebase offers two workflows to integrate with your existing processes:
- UI-Driven for complex migrations, hotfixes, or sensitive production changes
- Different workflows for different teams or projects

Both workflows share the same underlying CI/CD lifecycle, ensuring consistency regardless of how changes are initiated.
Both workflows share the same underlying CI/CD lifecycle, ensuring consistency regardless of how changes are initiated.
4 changes: 1 addition & 3 deletions mintlify/gitops/release.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,8 @@ Bytebase integrates with popular CI/CD platforms to automate database releases t

## Setup

Before creating releases:
Before creating releases, you'll need to [install the GitOps integration](/gitops/installation).

1. [Install GitOps Integration](/gitops/installation) - Connect Bytebase to your VCS
2. [Configure Database Environments](/administration/environment) - Set up your database environments (test, staging, production)

## Examples

Expand Down