Fix Travis-CI build & simplify Makefile & fix README

.github/workflows/build-test.yml

@@ -0,0 +1,53 @@
+name: Build & Test
+
+on: [push, pull_request]
+
+jobs:
+
+  build:
+    name: Build, Test & Run Tutorials
+    env:
+      MAIN_SRC_DIR: ./cmd/circuit/
+    runs-on: ubuntu-latest
+    steps:
+
+    - name: Set up Go
+      uses: actions/setup-go@v2
+      with:
+        go-version: ^1.13.1
+      id: go
+
+    - name: Check out code into the Go module directory
+      uses: actions/checkout@v2
+
+    - name: Get Go dependencies
+      run: go get -v -t -d ./...
+
+    - name: Create the bin directory (will ocntain the built binaries)
+      run: mkdir -p bin
+
+    - name: Build from Go sources
+      run: go build -v -o bin/circuit "$MAIN_SRC_DIR"
+
+    - name: Install the main executable into PATH
+      run: go install -v "$MAIN_SRC_DIR"
+
+    - name: Run Go Tests
+      run: go test ./...
+
+    - name: Build the Tutorials
+      run: |
+        go build -v -o bin/tutorial-nodejs-using-mysql ./tutorial/nodejs-using-mysql/start-app/
+        go build -v -o bin/tutorial-wait-all           ./tutorial/wait-all/
+        go build -v -o bin/tutorial-wait-first         ./tutorial/wait-first/
+        go build -v -o bin/tutorial-watchbot           ./tutorial/watchbot/
+        go build -v -o bin/tutorial-watchbot-with-chan ./tutorial/watchbot-with-chan/
+
+    - name: Run GoLang-CI Linter
+      run: |
+        # install it into ./bin/
+        curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s v1.25.1
+        # NOTE the " || true" chould possibly be removed from the below, once we reach 0 warnings
+        # NOTE " --enable-all" chould possibly be added to the below, to get more warnings
+        ./bin/golangci-lint run || true
+

.github/workflows/deploy-pages.yml

@@ -0,0 +1,50 @@
+name: Deploy Pages
+
+on:
+  push:
+    branches: [ master ]
+    paths:
+    - 'gocircuit.org/**'
+
+jobs:
+
+  build:
+    name: Build & Deploy Pages
+    env:
+      MAIN_SRC_DIR: ./cmd/circuit/
+    runs-on: ubuntu-latest
+    steps:
+
+    - name: Set up Go
+      uses: actions/setup-go@v2
+      with:
+        go-version: ^1.13.1
+      id: go
+
+    - name: Check out code into the Go module directory
+      uses: actions/checkout@v2
+
+    - name: Get Go dependencies
+      run: go get -v -t -d ./...
+
+    - name: Create the bin directory (will ocntain the built binaries)
+      run: mkdir -p bin
+
+    - name: Install the main executable into PATH
+      run: go install -v "$MAIN_SRC_DIR"
+
+    - name: Build the homepage
+      run: |
+        go build -v -o bin/build-homepage ./gocircuit.org/build
+        mkdir -p public
+        cd public
+        cp -r ../gocircuit.org/build/* ./
+        ../bin/build-homepage
+        cd ..
+
+    - name: Deploy to the gh-pages branch
+      uses: peaceiris/actions-gh-pages@v3
+      with:
+        github_token: ${{ secrets.GITHUB_TOKEN }}
+        publish_dir: ./public
+

.gitignore

@@ -1,3 +1,2 @@
-.hg
-.vagrant
-bin
+/bin/
+/public/

README.md

@@ -1,8 +1,9 @@
 # Circuit
 
-[![Build Status](https://drone.io/github.com/gocircuit/circuit/status.png)](https://drone.io/github.com/gocircuit/circuit/latest) [![GoDoc](https://godoc.org/github.com/gocircuit/circuit/client?status.png)](https://godoc.org/github.com/gocircuit/circuit/client)
+[![Build Status](https://travis-ci.org/hoijui/circuit.svg?branch=master)](https://travis-ci.org/hoijui/circuit)
+[![GoDoc](https://godoc.org/github.com/hoijui/circuit?status.png)](https://godoc.org/github.com/hoijui/circuit)
 
-![Engineering role separation.](https://raw.githubusercontent.com/gocircuit/circuit/master/misc/img/3.png)
+![Engineering role separation.](img/3.png)
 
 **The CIRCUIT is a new way of thinking. It is deceptively similar to existing software,
 while being quite different.**
@@ -15,7 +16,7 @@ Circuit was designed to enable clear, accountable and safe interface between the
 roles in a technology enterprise, ultimately increasing productivity. Engineering role separation
 in a typical circuit-based architecture is illustrated above.
 
-![A circuit-managed cloud.](https://raw.githubusercontent.com/gocircuit/circuit/master/misc/img/header.png)
+![A circuit-managed cloud.](img/header.png)
 
 Users of circuit are
 
@@ -61,7 +62,7 @@ programs in the [CSP](http://en.wikipedia.org/wiki/Communicating_sequential_proc
 which allows engineers to encode complex dynamic response behavior, spanning multiple data centers.
 
 Find comparisons to other technologies—like Zookeeper, etcd, CoreOS, raft, Consul, Puppet, Chef, and 
-so forth—in [the wiki](https://github.com/gocircuit/circuit/wiki).
+so forth—in [the wiki](https://github.com/hoijui/circuit/wiki).
 
 ## Incomparable but related works
 
@@ -99,7 +100,7 @@ Since this video was recorded, the API-via-file-system approach was abandoned
 in favor of a simpler command-line tool and a Go client library.
 
 Also take a look at the [faux animated illustration](https://docs.google.com/presentation/d/1nazPJAmYeIvJam9oiA-6euEz3Bo9flRLqsgRU7QAlr0/edit?usp=sharing)
-of the [Advanced Tutorial: Watchbot with a back channel](https://github.com/gocircuit/circuit/tree/master/tutorial/watchbot-with-chan).
+of the [Advanced Tutorial: Watchbot with a back channel](https://github.com/hoijui/circuit/tree/master/tutorial/watchbot-with-chan).
 
 The circuit is a tool for executing and synchronizing UNIX processes across entire clusters
 by means of a command-line tool and a client library.
@@ -114,7 +115,7 @@ The Circuit comprises one small binary. It can be built for Linux and Darwin.
 Given that the [Go Language](http://golang.org) compiler is [installed](http://golang.org/doc/install),
 you can build and install the circuit binary with one line:
 
-	go get github.com/gocircuit/circuit/cmd/circuit
+	go get github.com/hoijui/circuit/cmd/circuit
 
 ## Run the servers
 
@@ -154,7 +155,7 @@ This time, use the `-j` option to tell the new server to join the first one:
 You now have two mutually-aware circuit servers, running on two different
 hosts in your cluster. 
 
-![A circuit system of two hosts.](https://raw.githubusercontent.com/gocircuit/circuit/master/misc/img/servers.png)
+![A circuit system of two hosts.](img/servers.png)
 
 You can join any number of additional hosts to the circuit environment in a
 similar fashion, even billions.  The circuit uses a modern [expander
@@ -205,14 +206,14 @@ their anchor.
 
 Once the circuit servers are started, you can create, observe and control
 circuit elements (i) interactively—using the circuit binary which doubles as a command-line client—as
-well as (ii) programmatically—using the circuit Go client package `github.com/gocircuit/circuit/client`.
+well as (ii) programmatically—using the circuit Go client package `github.com/hoijui/circuit/client`.
 In fact, the circuit command-line tool is simply a front-end for the Go client library.
 
 Clients (the tool or your own) _dial into_ a circuit server in order to
 interact with the entire system. All servers are equal citizens in every respect and,
 in particular, any one can be used as a choice for dial-in.
 
-![Circuit client connected to a server](https://raw.githubusercontent.com/gocircuit/circuit/master/misc/img/client.png)
+![Circuit client connected to a server](img/client.png)
 
 The tool (described in more detail later) is essentially a set of commands that
 allow you to traverse the global hierarchical namespace of circuit elements,
@@ -230,7 +231,7 @@ So, you might get something like this in response
 
 The two root-level anchors correspond to the two circuit servers.
 
-![Circuit servers correspond to root-level anchors](https://raw.githubusercontent.com/gocircuit/circuit/master/misc/img/serveranchor.png)
+![Circuit servers correspond to root-level anchors](img/serveranchor.png)
 
 ### Pointing the tool to your circuit cluster ###
 
@@ -266,7 +267,7 @@ A list of available tool commands is shown on the help screen
 	circuit help
 
 A more detailed explanation of their meaning and function can be found
-in the documentation of the client package, `github.com/gocircuit/client`.
+in the documentation of the client package, `github.com/hoijui/circuit/client`.
 
 ### Example: Make a process ###
 
@@ -286,7 +287,7 @@ Run a new `ls` process:
 	}
 	EOF
 
-![Process elements execute OS processes on behalf of the user](https://raw.githubusercontent.com/gocircuit/circuit/master/misc/img/mkproc.png)
+![Process elements execute OS processes on behalf of the user](img/mkproc.png)
 
 See what happened:
 
@@ -334,7 +335,7 @@ To create and execute a new docker container, using the tool:
 Most of these fields can be omitted analogously to their command-line option counterparts 
 of the `docker` command-line tool.
 
-![Docker elements are like processes](https://raw.githubusercontent.com/gocircuit/circuit/master/misc/img/mkdkr.png)
+![Docker elements are like processes](img/mkdkr.png)
 
 The remaining docker element commands are identical to those for processes:
 `stdin`, `stdout`, `stderr`, `peek` and `wait`. In one exception, `peek` will return
@@ -356,7 +357,7 @@ let's create a channel on `X88550014d4c82e4d`:
 The last argument of this line is the channel buffer capacity,
 analogously to the way channels are created in Go.
 
-![Channel elements reside in the memory of a circuit server](https://raw.githubusercontent.com/gocircuit/circuit/master/misc/img/mkchan.png)
+![Channel elements reside in the memory of a circuit server](img/mkchan.png)
 
 Verify the channel was created:
 
@@ -477,11 +478,11 @@ Take a look, for instance, at the two “watchbot” tutorials which demonstrate
 how to implement a semi-resilient self-sustained mechanism within 
 a cluster. Find the simpler one here
 
-	https://github.com/gocircuit/circuit/tree/master/tutorial/watchbot
+	https://github.com/hoijui/circuit/tree/master/tutorial/watchbot
 
 And the more elaborate one, which demonstrate use of channels, here
 
-	https://github.com/gocircuit/circuit/tree/master/tutorial/watchbot-with-chan
+	https://github.com/hoijui/circuit/tree/master/tutorial/watchbot-with-chan
 
 ## Security ##
 
@@ -522,20 +523,20 @@ Ask questions to [The Circuit User Group](https://groups.google.com/forum/#!foru
 
 The Go client for writing circuit apps is package
 
-	github.com/gocircuit/circuit/client
+	github.com/hoijui/circuit/client
 
 The public interface of this package is self-contained. Other
 packages in the circuit repo are internal.
 
 Tutorials can be found within the client package directory
 
-	github.com/gocircuit/circuit/client/tutorial
+	github.com/hoijui/circuit/client/tutorial
 
 Additionally, the circuit binary directory contains the implementation
 of the circuit tool, which is itself built using the client and is another
 comprehensive example of a circuit app. It can be found in
 
-	github.com/gocircuit/circuit/cmd/circuit
+	github.com/hoijui/circuit/cmd/circuit
 
 To stay up to date with new developments, documentation and articles, follow
 The Circuit Project on Twitter [@gocircuit](https://twitter.com/gocircuit) or

TODO

@@ -12,3 +12,4 @@ test coverage
 job scheduler ala mesos
 add mutex element
 tty element; interactive shell
+use external dependencies instead of local ./github.com/... and ./gocircuit.org/...

cmd/circuit/chan.go

@@ -13,10 +13,10 @@ import (
 	"os"
 	"strconv"
 
-	"github.com/gocircuit/circuit/client"
+	"github.com/hoijui/circuit/pkg/client"
 	"github.com/pkg/errors"
 
-	"github.com/urfave/cli"
+	"github.com/urfave/cli/v2"
 )
 
 // circuit mkchan /X1234/hola/charlie 0
@@ -29,12 +29,12 @@ func mkchan(x *cli.Context) (err error) {
 
 	c := dial(x)
 	args := x.Args()
-	if len(args) != 2 {
+	if x.NArg() != 2 {
 		return errors.New("mkchan needs an anchor and a capacity arguments")
 	}
-	w, _ := parseGlob(args[0])
+	w, _ := parseGlob(args.Get(0))
 	a := c.Walk(w)
-	n, err := strconv.Atoi(args[1])
+	n, err := strconv.Atoi(args.Get(1))
 	if err != nil || n < 0 {
 		return errors.New("second argument to mkchan must be a non-negative integral capacity")
 	}
@@ -53,10 +53,10 @@ func send(x *cli.Context) (err error) {
 
 	c := dial(x)
 	args := x.Args()
-	if len(args) != 1 {
+	if x.NArg() != 1 {
 		return errors.New("send needs one anchor argument")
 	}
-	w, _ := parseGlob(args[0])
+	w, _ := parseGlob(args.Get(0))
 	u, ok := c.Walk(w).Get().(client.Chan)
 	if !ok {
 		return errors.New("not a channel")
@@ -74,10 +74,10 @@ func send(x *cli.Context) (err error) {
 func clos(x *cli.Context) (err error) {
 	c := dial(x)
 	args := x.Args()
-	if len(args) != 1 {
+	if x.NArg() != 1 {
 		return errors.New("close needs one anchor argument")
 	}
-	w, _ := parseGlob(args[0])
+	w, _ := parseGlob(args.Get(0))
 	u, ok := c.Walk(w).Get().(client.Chan)
 	if !ok {
 		return errors.New("not a channel")