Skip to main content

​
Introduction

Applications represent a Laravel application that is deployed to Laravel Cloud. Applications can be created from official Laravel starter kits or from existing GitHub, Bitbucket, or GitLab repositories. Applications can contain many environments and resources.

​
Creating applications

Laravel Cloud offers two ways to create applications:
  1. From Starter Kits - Bootstrap a new application using official Laravel starter kits
  2. From Existing Repository - Import and deploy from your existing Git repository
Both methods require selecting a region where your application will be deployed. Currently, an application can only be deployed to a single region at a time. Laravel Cloud will automatically create a default environment for your application regardless of the creation method you choose.
Applications cannot be transferred between organizations once created. Applications are permanently associated with the organization they are created in.

​
Creating from starter kits

Laravel Cloud supports creating applications from official Laravel starter kits, allowing you to deploy a production-ready Laravel application in minutes without needing an existing repository.

​
Available starter kits

Laravel Cloud provides the following official starter kit templates:

​
Creating from a starter kit

When creating an application from a starter kit:
  1. Select “Use a template” from the application creation page
  2. Choose your desired starter kit template
  3. Configure your Git provider account (if not already connected)
  4. Set your repository name and choose visibility (private or public)
  5. Assign an application name
  6. Select your deployment region
The starter kit will automatically create a new repository in your connected Git provider account, clone the official Laravel starter kit code, and set up your application for deployment.
Starter kit applications work exactly like any other Laravel application on Laravel Cloud. Once deployed, you can customize, extend, and deploy changes just like applications created from existing repositories.

​
Creating from existing repository

When creating an application from an existing repository, you will need to select a source control repository that the application should be deployed from, assign the application a name, and select a region. If you have not already linked a source control provider account to your organization, you will be prompted to do so when you create your application. Typically, your Laravel Cloud organization structure should mirror your source control provider organization structure.
After a source control provider has been authenticated, the repository (or repositories) selected become available for all users in the organization to view and create applications from.

​
Regions

Laravel Cloud currently supports the following application regions:
  • US East (Virginia) / us-east-1
  • US East (Ohio) / us-east-2
  • CA Central (Central) / ca-central-1
  • EU Central (Frankfurt) / eu-central-1
  • EU West (Ireland) / eu-west-1
  • EU West (London) / eu-west-2
  • Asia Pacific (Singapore) / ap-southeast-1
  • Asia Pacific (Sydney) / ap-southeast-2
For minimal latency, you should ensure that your application and its associated resources exist within the same region.

​
Deleting applications

When deleting applications, all environments within that application will be deleted; however, resources such as databases, key-value stores ,and object storage buckets are not deleted, since they may be used by other applications within the environment. To delete these resources, navigate to your organization’s “Resources” tab.

​
Troubleshooting

​
Reconnect Git repository

Applications can lose their connection to a Git repository if Laravel Cloud’s API access is revoked from within the source control provider. When this happens, your application’s environments can no longer deploy your latest changes. Follow these steps to restore your Git connection:
  1. Navigate to your applications “Settings” page.
  2. Click the “Not connected” button next to “Git repository”.
  1. Click the “Source control provider” dropdown to select an existing source control provider or connect a new one by clicking “Add account”.
  2. Select the right repository, click “Set repository”, then click “Save”.
Your application’s Git repository is now restored and you can resume deploying fresh code to your environments.
In most cases environment branches will be restored automatically; however, there may be some cases where environment branches need to be manually selected and saved via the environment “Settings” tab.