From 2074d65853c6e57ebc4ab4c80ac96d9e59a25be5 Mon Sep 17 00:00:00 2001 From: Alex Renoki Date: Tue, 18 Aug 2020 20:29:23 +0300 Subject: [PATCH] wip faq [skip ci] --- docs/faq/deploying.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/faq/deploying.md b/docs/faq/deploying.md index 7c49a476a6..8cca2dc58d 100644 --- a/docs/faq/deploying.md +++ b/docs/faq/deploying.md @@ -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.