You may also need to configure the additional GitOps Webhook URL if the public endpoint is different
than the internal one.
For testing purpose, you can get an endpoint online with ngrok as external URL.When running Bytebase in production, you should not make the node that’s running the Bytebase server directly accessible to the client. Instead, you should set up an gateway such as Nginx or Caddy to forward requests to Bytebase.Logically, you need to configure 2 endpoints, the external URL that users use to access the Bytebase console, and the GitOps Webhook URL that the VCS pushes the webhook event for GitOps workflow. The former usually is accessed from
the internal network, while the latter may come from the external network if using GitHub.com / GitLab.com.
If they both can be accessed via the same endpoint, then you only need to configure the external URL:
If internal network access is different than external (e.g. bytebase.example.dev vs bytebase.example.com), you need to configure a separate GitOps Webhook URL:
This will persist the External URL setting. Thus if Bytebase starts without specifying —external-url
next time, the previously passed External URL value will still be there.