summaryrefslogtreecommitdiff
path: root/Run/Que/index.md
diff options
context:
space:
mode:
authorBen Sima <ben@bsima.me>2020-03-31 17:12:09 -0700
committerBen Sima <ben@bsima.me>2020-03-31 17:12:09 -0700
commit9493e2dbf9671d55fea2a96aa057589670e9673a (patch)
tree6702a9bc37826d8fd1f522a7ab16a7a2b696447d /Run/Que/index.md
parent721cca4b1372e222c6841ddc57bb952271d72dc7 (diff)
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.
Diffstat (limited to 'Run/Que/index.md')
-rw-r--r--Run/Que/index.md47
1 files changed, 8 insertions, 39 deletions
diff --git a/Run/Que/index.md b/Run/Que/index.md
index b619de7..59a7ad8 100644
--- a/Run/Que/index.md
+++ b/Run/Que/index.md
@@ -12,7 +12,7 @@ que is the concurrent, async runtime in the cloud
HTTP routes on que.run are Golang-like channels with a namespace and a
path. For example: `https://que.run/example/path/subpath`.
-## download the client
+## Quickstart
There is a simple script `que` that acts as a client you can use to
interact with the `que.run` service.
@@ -25,44 +25,13 @@ Download it to somewhere on your `$PATH` and make it executable:
The client requires a recent version of Python 3.
-## examples
+## Quescripts
-Here are some example applications, I will update these in the coming
-weeks with additional useful scripts.
+We are collecting a repository of scripts that make awesome use of que:
-### desktop notifications
+- remote desktop notifications
+- two-way communication with your phone
+- ephemeral, serverless chat rooms
+- collaborative jukebox
-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...
+<a id="quescripts-btn" href="_page/quescripts">See the examples</a>