Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

Commit

Permalink
wip faq [skip ci]
Browse files Browse the repository at this point in the history
  • Loading branch information
rennokki committed Aug 18, 2020
1 parent 3b49bcd commit 2074d65
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions docs/faq/deploying.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,12 @@ sudo pecl install event

If your are using [Laravel Forge](https://forge.laravel.com/) for the deployment [this article by Alex Bouma](https://alex.bouma.dev/installing-laravel-websockets-on-forge) might help you out.

#### Deploying on Laravel Vapor

Since [Laravel Vapor](https://vapor.laravel.com) runs on a serverless architecture, you will need to spin up an actual EC2 Instance that runs in the same VPC as the Lambda function to be able to make use of the WebSocket connection.

The Lambda function will make sure your HTTP request gets fulfilled, then the EC2 Instance will be continuously polled through the WebSocket protocol.

## Keeping the socket server running with supervisord

The `websockets:serve` daemon needs to always be running in order to accept connections. This is a prime use case for `supervisor`, a task runner on Linux.
Expand Down

0 comments on commit 2074d65

Please sign in to comment.