From 96074a78599be980f967f3b07e16dc5b9b56723d Mon Sep 17 00:00:00 2001 From: Serge Bazanski Date: Thu, 30 Jul 2020 21:41:56 +0200 Subject: [PATCH] laserproxy: document deployment Change-Id: I4461b8c392f79781247605315b2e1b744bbb1acb --- hswaw/laserproxy/README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/hswaw/laserproxy/README.md b/hswaw/laserproxy/README.md index 3a2e8dbb..56af4b7b 100644 --- a/hswaw/laserproxy/README.md +++ b/hswaw/laserproxy/README.md @@ -15,3 +15,14 @@ Only one user is allowed at a time - to implement this mutual exclusion, a Locke A lock is taken through a web interface by the user that wants to access the laser. When a lock is taken, the Locker will notify a Proxy worker about this address. The Proxy will then perform the UDP proxying. As traffic is proxied, the Proxy will send bump updates to the Locker to extend the lock deadline. + +Deployment +---------- + +You'll need root access to customs. + + bazel build --platforms=@io_bazel_rules_go//go/toolchain:openbsd_amd64 //hswaw/laserproxy + ssh root@customs supervisorctl stop laserproxy + scp bazel-bin/hswaw/laserproxy/laserproxy_/laserproxy root@customs:/var/laserproxy/laserproxy + ssh root@customs supervisorctl start laserproxy +