Introduction
Laravel Cloud deploys your application by connecting to a Git provider. Cloud supports GitHub, GitLab, and Bitbucket.
Connecting a source control provider
To connect a source control provider, go to “Account settings > Source controls”.
Select a provider and go through the OAuth flow to authorize the connection.
For GitHub, you may be asked to install the Laravel Cloud App on the GitHub account or organization that owns your repositories. This controls which repositories Cloud can access. GitLab and Bitbucket do not require this step.
Disconnecting a source control provider
You can disconnect a provider from “Account settings > Source control”. Click the ”…” next to the provider and then “Disconnect”.
This will affect all applications that rely on that connection, across all of your organizations. Those applications will continue running but will not be able to deploy until the repository is reconnected by you or another user with access to the repository.
Refreshing tokens
If your provider token expires or you need to re-authorize access, go to “Account settings > Source control”, click the ”…” next to the provider, and then “Reauthorize”.
Troubleshooting
Connecting the same Git account to a second Cloud user
OAuth allows only one Laravel Cloud user per Git provider personal account, so a given GitHub, GitLab, or Bitbucket account can be linked to a single Cloud user.
If your GitHub user “johndoe” is already connected to one Cloud account, it cannot also be connected to a different Cloud account.
To work across multiple organizations, create additional organizations under the same Cloud account rather than creating a separate Cloud user.
Missing repositories
If you can’t see a repository in your list, check that:
- You have access to that repository on the provider’s side. Laravel Cloud follows the provider’s permissions.
- (If you’re using GitHub) The Laravel Cloud App is installed on the account or organization that owns the repository.
