You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This guide explains the network connectivity options for Bytebase features that require external access, including GitOps workflows, SSO authentication, and webhooks.
6
+
7
+
## Features Requiring External Access
8
+
9
+
-**GitOps Workflows**: CI/CD platforms (GitHub Actions, GitLab CI, etc.) need to call Bytebase API
10
+
-**SSO Authentication**: OAuth2/OIDC/SAML providers need callback access
11
+
-**Webhooks**: External services sending events to Bytebase
12
+
13
+
## Three Network Patterns
14
+
15
+
### 1. Bytebase Cloud
16
+
Use [Bytebase Cloud](https://hub.bytebase.com/) for instant setup without infrastructure management. External services connect directly.
17
+
18
+
**Best for:** Quick testing, evaluation, and small teams
19
+
20
+
### 2. Self-Hosted Bytebase (Production)
21
+
22
+
Keep Bytebase inside your private network for security.
- Install self-hosted runners/agents inside your network
32
+
- Runners connect to your internal Bytebase without exposing it to the internet
33
+
34
+
**Best for:** Production setups with strict network boundaries.
35
+
36
+
### 3. Self-Hosted Local Testing with Reverse Proxy
37
+
38
+
Temporarily expose local Bytebase for testing using reverse proxy tools such as:
39
+
-[ngrok](https://ngrok.com/)
40
+
-[VS Code port forwarding](https://code.visualstudio.com/docs/editor/port-forwarding)
41
+
- Other tunneling services
42
+
43
+
<Warning>
44
+
Never use reverse proxy tools in production. They are for local testing only.
45
+
</Warning>
46
+
47
+
<Info>
48
+
**Important for Self-Hosted:** Remember to configure the External URL in Bytebase **Settings > General** with your public URL for SSO callbacks and other integrations to work properly.
Copy file name to clipboardExpand all lines: mintlify/gitops/installation.mdx
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,13 @@
1
1
---
2
2
title: Installation
3
-
description: Installation and setup guide for connecting Version Control Systems with Bytebase
4
3
---
5
4
6
5
This guide covers the setup requirements for connecting Version Control Systems (VCS) with Bytebase.
7
6
7
+
<Info>
8
+
For understanding network patterns and external access options, see the [Network Architecture guide](/get-started/self-host/network-architecture).
9
+
</Info>
10
+
8
11
## Bytebase Cloud
9
12
10
13
**No installation required** for cloud VCS providers:
@@ -51,3 +54,10 @@ When using cloud VCS with self-hosted Bytebase, you need a self-hosted runner:
51
54
- Network policies allow communication
52
55
- If your GitLab runner lacks internet access, pre-load the bytebase-action Docker image
53
56
57
+
## Local Testing
58
+
59
+
To expose local Bytebase for testing with cloud VCS services, use reverse proxy tools like ngrok. See [Network Architecture guide](/get-started/self-host/network-architecture#3-self-hosted-local-testing-with-reverse-proxy) for setup details.
60
+
61
+
<Warning>
62
+
For development and testing only. Never use in production.
Use [Bytebase Cloud](https://hub.bytebase.com/) for instant setup without infrastructure management. CI/CD services can connect immediately.
6
+
7
+
**Best for:** Quick testing, evaluation, and small teams
8
+
</Tab>
9
+
<Tabtitle="Self-Hosted">
10
+
Run Bytebase in Docker within your infrastructure:
11
+
12
+
<TerminalDockerRunVolume />
13
+
14
+
**Network Access Options:**
15
+
16
+
- **For testing:** Use tools such as [ngrok](https://ngrok.com/) or [VS Code port forwarding](https://code.visualstudio.com/docs/editor/port-forwarding) to temporarily expose your local Bytebase to cloud CI/CD services. After exposing, configure the **External URL** in Bytebase **Settings > General**.
17
+
18
+
- **For production:** Use self-hosted CI/CD runners within your private network. Never expose production Bytebase to the internet.
19
+
20
+
**Best for:** Organizations with security requirements or existing infrastructure
21
+
</Tab>
22
+
</Tabs>
23
+
24
+
See [Network Architecture guide](/get-started/self-host/network-architecture#2-self-hosted-bytebase-production).
@@ -60,7 +61,7 @@ This tutorial code repository is at [https://dev.azure.com/bytebase-hq/\_git/byt
60
61
61
62
1. Go into `pipelines/sql-review.yml` and `pipelines/rollout-release.yml`. In the `env` section, replace the variable values with your own and commit the changes.
62
63
63
-
-**BYTEBASE_URL**: your ngrok url
64
+
-**BYTEBASE_URL**: Your Bytebase instance URL (e.g., `https://bytebase.your-company.com` or your Bytebase Cloud URL)
64
65
-**BYTEBASE_SERVICE_ACCOUNT**: `[email protected]` (the service account you created in the previous step)
65
66
-**BYTEBASE_PROJECT**: `projects/project-sample` (the sample project in the Bytebase)
66
67
-**BYTEBASE_TARGETS**: `instances/test-sample-instance/databases/hr_test,instances/prod-sample-instance/databases/hr_prod` (the two default databases in the sample project)
1. Go into `.github/workflows/release-action.yml` and `.github/workflows/sql-review-action.yml`. In the `env` section, replace the variable values with your own and commit the changes.
75
76
76
-
-**BYTEBASE_URL**: your ngrok url
77
+
-**BYTEBASE_URL**: Your Bytebase instance URL (e.g., `https://bytebase.your-company.com` or your Bytebase Cloud URL)
77
78
-**BYTEBASE_SERVICE_ACCOUNT**: `[email protected]` (the service account you created in the previous step)
78
79
-**BYTEBASE_PROJECT**: `projects/project-sample` (the sample project in the Bytebase)
79
80
-**BYTEBASE_TARGETS**: `instances/test-sample-instance/databases/hr_test,instances/prod-sample-instance/databases/hr_prod` (the two default databases in the sample project)
@@ -182,7 +183,7 @@ Team members can trigger deployments by commenting `/migrate <environment>` on a
182
183
183
184
1. Go into `.github/workflows/chatops-migrate.yml`. In the `env` section, replace the variable values with your own:
184
185
185
-
-**BYTEBASE_URL**: your ngrok url
186
+
-**BYTEBASE_URL**: Your Bytebase instance URL (e.g., `https://bytebase.your-company.com` or your Bytebase Cloud URL)
0 commit comments