Nulo/localfirst-relay-deployable
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity

README.md: update

Browse source
This commit is contained in:
HerbCaudill 2020-12-18 12:23:17 +01:00
parent 914ea5d407
commit 18af0a9744
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -9,11 +9,11 @@ Jump to instructions for:
[AWS](#deploying-to-aws-elastic-beanstalk) |
[Google](#deploying-to-google-cloud) |
[Azure](#deploying-to-azure) |
[local deployment](#installing-and-running-locally)
[local server](#installing-and-running-locally)
## Deploying to Glitch
You can deploy this relay to [Glitch](https://glitch.com) by clicking this button
You can deploy this relay to [Glitch](https://glitch.com) by clicking this button:
[![Remix on Glitch](https://cdn.glitch.com/2703baf2-b643-4da7-ab91-7ee2a2d00b5b%2Fremix-button.svg)](https://glitch.com/edit/#!/import/github/local-first-web/relay-deployable)
@ -91,4 +91,6 @@ You can visit that address with a web browser to confirm that it's active. If it
## AWS Lambda, Azure Functions, Vercel, Serverless, Cloudwatch Workers, etc.
Since true serverless functions are stateless and only spun up on demand, they're not a good fit for this server, which needs to remember information about connected peers and maintain a stable websocket connection with each one.
Since true serverless functions are stateless and only spun up on demand, they're not a good fit for
this server, which needs to remember information about connected peers and maintain a stable
websocket connection with each one.