[error] Access forbidden by rule
Like most websites on the internet, your site will often see bots scanning it for vulnerabilities. When a bot requests a page that does not exist, or a page that Laravel Cloud blocks for security purposes, you may see related[error] logs. You can safely ignore these logs.
fatal: not a git repository
Some packages may attempt to access your.git directory while your application is running. Laravel Cloud removes the .git folder during the deploy process, so the directory is unavailable at runtime. Packages that depend on the .git directory can then trigger this error. For example, Sentry gives you the option to run Git to grab the current commit hash, which triggers these errors.
If a package depends on your deployment’s Git hash being available, you can inject it as an environment variable by adding the following to your build commands:
[truncated due size]
The[truncated due size...] message means that a log message exceeded a size limit and was cut off. Long logs and error messages cause this, and it is common during deployments. To reduce the output of your deploy commands, add flags that make the commands less verbose:
APP_DEBUG=true, errors produce a full stack trace, which can also be truncated.