AnySites

// GETTING STARTED

Connect Your Git Account

Authorize GitHub via OAuth, or connect a self-hosted GitLab instance with a personal access token.

GitHub

Click Connect GitHub in Settings. This starts an OAuth flow (GET /api/auth/oauth/github); after you authorize, the access token is encrypted and stored against your account. AnySites uses this token to read your repositories and to register push webhooks — it never asks for your GitHub password.

GitLab

Because many GitLab instances are self-hosted and not publicly reachable for an OAuth callback, GitLab connects differently: you paste a Personal Access Token and the instance's base URL (e.g. https://gitlab.example.com). Use a token scoped to api and read_repository at minimum — webhook creation needs write access to the repository's webhook settings.

You can add multiple GitLab connections — for example one for gitlab.com and one for a company-internal instance. Use Test connection after adding one; it calls the instance's API with your token and confirms the username it resolves to.

A GitLab Personal Access Token has an expiry date if you set one. When it expires, webhook registration and repository listing silently start failing for every project on that connection — there's currently no expiry warning in the UI, so if auto-deploy stops working for multiple projects at once, check the token first.

Related documentation