@if (count($application->additional_servers) > 0)
Previews will be deployed on {{ $application->destination->server->name }}.
@endif
@if ($application->is_github_based())
@can('update', $application)

Pull Requests on Git

Load Pull Requests @endcan
@endif @isset($rate_limit_remaining)
Requests remaining till rate limited by Git: {{ $rate_limit_remaining }}
@endisset
@if ($pull_requests->count() > 0)
@foreach ($pull_requests as $pull_request) @endforeach
PR Number PR Title Git Actions
{{ data_get($pull_request, 'number') }} {{ data_get($pull_request, 'title') }} Open PR on Git @can('update', $application) Configure @endcan @can('deploy', $application) Deploy @endcan
@endif
@if ($application->previews->count() > 0)

Deployments

@foreach (data_get($application, 'previews') as $previewName => $preview)
PR #{{ data_get($preview, 'pull_request_id') }} | @if (str(data_get($preview, 'status'))->startsWith('running')) @elseif(str(data_get($preview, 'status'))->startsWith('restarting')) @else @endif @if (data_get($preview, 'status') !== 'exited') | Open Preview @endif | Open PR on Git @if (count($parameters) > 0) | Deployment Logs | Application Logs @endif
@if ($application->build_pack === 'dockercompose')
@if (collect(json_decode($preview->docker_compose_domains))->count() === 0)
@can('update', $application) Save Generate Domain @endcan
@else @foreach (collect(json_decode($preview->docker_compose_domains)) as $serviceName => $service) @endforeach @endif
@else
@can('update', $application) Save Generate Domain @endcan
@endif
@can('deploy', $application) Force deploy (without cache) @if (data_get($preview, 'status') === 'exited') Deploy @else Redeploy @endif @endcan @if (data_get($preview, 'status') !== 'exited') @can('deploy', $application) Stop @endcan @endif @can('delete', $application) @endcan
@endforeach
@endif The preview deployment domain is already in use by other resources. Using the same domain for multiple resources can cause routing conflicts and unpredictable behavior.
  • The preview deployment may not be accessible
  • Conflicts with production or other preview deployments
  • SSL certificates might not work correctly
  • Unpredictable routing behavior