Build on your own server (SSH + BaoTa)

Build on your own server: you keep full control of the server and files, and GOCO deploys the generated sites onto it over SSH.

Key order: create sites in BaoTa first, then deploy from GOCO

When deploying a build, GOCO only writes the generated site files into the site root (webroot); it doesn’t touch your nginx vhost. So the site directory and domain binding must already exist in BaoTa before the platform can deploy into it. (Two other places do reach the panel: SSL deployment / renewal writes the certificate into the matching site and reloads nginx; and onboarding a server writes an SSH keep-alive snippet sshd_config.d/99-goco.conf (heartbeat + concurrency) and reloads sshd. Both are rollback-safe, self-contained snippets that leave your own config alone.)

Before you start

• A cloud server / VPS (2 cores or more recommended).
• The BaoTa panel installed on it.
• A GOCO account (each account has 10 free build credits, shared between SSH and managed hosting).

Steps

1. Install the BaoTa panel

   Install BaoTa on your server from its official site; log in and make sure the panel port is open and reachable.

   Go to BaoTa’s site ↗

2. Create default sites in BaoTa

   For every domain you’ll build, add the site in BaoTa under Websites → Add site: enter the domain, generate the site root (webroot), enable SSL if needed. Creating this batch of default sites up front makes the later bulk deploy smooth.

3. Bind the server on GOCO + buy a license

   On the console Servers page, add your server: host, SSH port, SSH username, password or private key, then Test connection (the platform writes an SSH keep-alive / concurrency-tuning snippet under sshd_config.d/). Then buy a build license for that server, or try it on your account’s free build credits (10 credits, shared between SSH and managed hosting).

   Add a server ↗

4. New batch (choose “your own server”)

   Batches → New batch. In Step 1 choose your own server and select the one you just bound, then the template-assignment mode, HTML templates and the domain list (matching the sites you created in BaoTa).

5. Advanced config (optional)

   Configure brand, content and SEO tools. See the shared notes in the overview.

6. Review & submit (deploy)

   In Step 3 review the site list and submit. GOCO deploys the generated files to the matching site roots on your server over SSH.

7. SSL certificates

   On the SSL page, acme.sh issues and auto-renews certificates onto your server before expiry — zero maintenance.

After

On the Sites page review each site’s status and health, then enable scheduled publishing, SEO, indexing and CloudFlare bulk management.

Back to overview