From 9493e2dbf9671d55fea2a96aa057589670e9673a Mon Sep 17 00:00:00 2001 From: Ben Sima Date: Tue, 31 Mar 2020 17:12:09 -0700 Subject: Massively improve the que-website curl was throwing an exception if the file got too long, because I was passing the entire file contents in the arguments to curl. I tried using a tmp file but that didn't work for some reason. So I switched to req and that seems to work well. I also made it faster by serving all pages concurrently, and I spruced up the CSS a ton. --- Run/Que/quescripts.md | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 Run/Que/quescripts.md (limited to 'Run/Que/quescripts.md') diff --git a/Run/Que/quescripts.md b/Run/Que/quescripts.md new file mode 100644 index 0000000..204328a --- /dev/null +++ b/Run/Que/quescripts.md @@ -0,0 +1,38 @@ +% Quescripts + +## Remote desktop notifications + +Lets say we are running a job that takes a long time, maybe we are +compiling or running a large test suite. Instead of watching the +terminal until it completes, or flipping back to check on it every so +often, we can create a listener that displays a popup notification when +the job finishes. + +In one terminal run the listener: + + que example/notify --then "notify-send '\que' '\msg'" + +In some other terminal run the job that takes forever: + + runtests ; echo "tests are done" | que example/notify - + +When terminal 2 succeeds, terminal 1 will print "tests are done", then +call the `notify-send` command, which displays a notification toast in +Linux with title "`example/notify`" and content "`tests are done`". + +Que paths are multi-producer and multi-consumer, so you can add as many +terminals as you want. + +On macOS you could use: + + osascript -e 'display notification "\msg" with title "\que"' + +in place of notify-send. + +## Ephemeral, serverless chat rooms + +coming soon + +## Collaborative jukebox + +coming soon -- cgit v1.2.3