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

Commit 2074d65

Browse files
committed
wip faq [skip ci]
1 parent 3b49bcd commit 2074d65

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/faq/deploying.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,12 @@ sudo pecl install event
4747

4848
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.
4949

50+
#### Deploying on Laravel Vapor
51+
52+
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.
53+
54+
The Lambda function will make sure your HTTP request gets fulfilled, then the EC2 Instance will be continuously polled through the WebSocket protocol.
55+
5056
## Keeping the socket server running with supervisord
5157

5258
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.

0 commit comments

Comments
 (0)