Skip to main content

Documentation Index

Fetch the complete documentation index at: https://cloud.laravel.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Topics

​
Git

GitHubYou can manage your installation of the “Laravel Cloud App” GitHub application by going to GitHub > Settings > Integrations: Applications > Laravel Cloud App > Configure. From there you can update the Repository access settings or suspend/uninstall the integration.GitLabYou can manage your installation of the “Laravel Cloud” GitLab application by going to GitLab > Preferences > Applications. From there you revoke Cloud’s access to your account.BitBucketYou can manage your installation of the “Laravel Cloud” BitBucket integration by going to BitBucket > Settings > Workspace settings > OAuth consumers. From there you revoke Cloud’s access to your account.
If you are using GitLab or BitBucket as your source control provider, you should be mindful when making permissions changes to repositories or managing webhooks within the source control provider’s UI. Making changes here may prevent Cloud’s push to deploy functionality from working correctly or prevent Cloud from being able to clone your repository during deployment.

​
Custom domains

If your domain is stuck verifying or timed out, common causes include incorrect record names, adding records in the wrong DNS provider, or Cloudflare proxy and DNS-only conflicts.For detailed troubleshooting steps, check out our docs on verifying domains or review the Domains guide.
Wildcard domains require pre-verification and a DCV delegation record so SSL certificates can continue to be issued and renewed. Both the wildcard domain and the root domain must be configured.Refer to our docs on wildcard domains for complete setup details.

​
URLs

​
Logs

Laravel Cloud will automatically configure your environment to use the stderr log channel using JSON formatting. This is required in order for logs to be formatted correctly in the Cloud UI.By default stack traces are not captured by Laravel Cloud. You may include stack traces by enabling includeStacktraces within the stderr channel in your application’s logging.php configuration.
PHP
'stderr' => [
    'driver' => 'monolog',
    'level' => env('LOG_LEVEL', 'debug'),
    'handler' => StreamHandler::class,
    'formatter' => env('LOG_STDERR_FORMATTER', JsonFormatter::class),
    'formatter_with' => [
        'includeStacktraces' => true,
    ],
    'with' => [
        'stream' => 'php://stderr',
    ],
    'processors' => [PsrLogMessageProcessor::class],
],
Of course, you may also use any of Laravel’s supported external log providers should you prefer.