From 04b350d5986a8bb79baf9ee4e40c79226db91a4d Mon Sep 17 00:00:00 2001 From: Adam Doyle Date: Tue, 8 Oct 2024 21:59:48 -0400 Subject: [PATCH] update readme --- readme.md | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/readme.md b/readme.md index b434040..c8d2f69 100644 --- a/readme.md +++ b/readme.md @@ -17,15 +17,13 @@ With auto-reload: Then: ```sh -watch -i client -cx run +./test ``` -or if you're lazy like me just run `./test` - Without auto-reload: ```sh -cargo run +cargo run -p server ``` ### Client @@ -54,20 +52,30 @@ cargo build --release --- -- The server automatically serves the built client from `/dist` at `127.0.0.1:3030`. When building for release the client automatically points to doordesk +- The server automatically serves the built client from `/dist` at `127.0.0.1:3030`. When building for release the client automatically points to doordesk. -- Configure any custom clients to connect to `ws://127.0.0.1:3030/websocket` for local testing or `wss://cards.doordesk.net/websocket` to use my server +- Configure any custom clients to connect to `ws://127.0.0.1:3030/websocket` for local testing or `wss://cards.doordesk.net/websocket` to use my server. ## Tools: There is a tool named socket_blaster used for stress testing the server. Run + ```sh cargo run -p socket_blaster -- -h ``` + to see available options. +Then + +```sh +cargo run -p socket_blaster -- [COMMAND] +``` + +to run a command. + ## TODO: - prevent zombie users after browser crash