Beta guide

Welcome, grey captain. The Greyship beta is open. This is your chance to build with Greyship on our beta instance, before it becomes strictly self-hosted. Read this page, deploy a Go web service, and tell us what you think.

1. Sign in to the dashboardCopy Anchor Link

Open app.greyship.tech and sign in with the email address the newsletter came to and the password it gave you. There is no signup and no email code: the instance's admin made your account.

The password in the newsletter is the same for everyone. Change it under Settings → Password once you're in. Forgot it later? Message me and I'll reset it.

2. Deploy a Go web service: web or terminal, your pickCopy Anchor Link

The dashboard and the grey CLI do the same things, so use whichever you like, or both. Everything you do in one shows up in the other. The full list is in Use the dashboard.

In the dashboardCopy Anchor Link

Open New project. Import from GitHub (one click to create your own GitHub App, then install it on a repo) or paste a public repository's link. Greyship shows the services it found, you set env vars, press Deploy and watch the build log. Then use the project's Logs, Env, Domains, Deployments (redeploy and roll back) and Settings pages. See Use the dashboard and Deploy from GitHub.

With the CLICopy Anchor Link

curl -fsSL https://greyship.tech/cli/install | sh
grey server https://app.greyship.tech
grey login
grey deploy

1. The first line installs grey.
2. grey server https://app.greyship.tech tells it which Greyship to talk to: our beta instance. grey works with any Greyship, yours included, so it needs this once. Run grey server with no address any time to see which one it uses.
3. grey login opens your browser so you can approve the login with your account.
4. grey deploy in any Go project (a folder with a go.mod) builds it, switches traffic over only when the new version is healthy, and prints its URL.

Update grey any time with grey upgrade. More in Install the CLI and the Quickstart.

Idle services pause and wake on the next request. See also Deploys, Environment variables and Logs.

Good to know during the betaCopy Anchor Link

• Builds run one at a time, so a deploy may wait behind someone else's build. The CLI tells you how many are ahead of you.
• Limits. The admin can limit how much memory and CPU each person's apps use (see Limits). A deploy over your limit fails with a message that says so, and the live version keeps running.
• It is a beta. Expect rough edges, and don't put anything you can't lose on it. Some features are rolling out during the beta: importing from GitHub with your own GitHub App, custom domains, and deleting projects from Settings. If a page in these docs describes something you can't see yet, it's on its way.
• You can run it yourself. Greyship is open source and installs on your own server with one command: see Install Greyship (self-hosting) and github.com/greylabss/greyship.

Tell me what you thinkCopy Anchor Link

Bugs, rough edges, ideas, "this confused me": all of it helps. My DMs are open:

• X: x.com/shellhaki
• Email: shellhaki@gmail.com
• WhatsApp: wa.me/shellhakii
• Beta forum (WhatsApp group): join here

When you report something, tell me what you ran, what you expected and what happened. The deployment's id from grey deploy makes a build problem easy for me to look up.