Merge pull request #20 from picostack/rebrand

rebrand from wadsworth to picobot

Author: Southclaws

.gitignore

@@ -19,7 +19,7 @@
 .env
 
 # The binary
-wadsworth
+picobot
 dist
 .env
 cache

.goreleaser.yml

@@ -1,4 +1,4 @@
-project_name: wadsworth
+project_name: picobot
 builds:
   - env:
       - CGO_ENABLED=0
@@ -22,13 +22,13 @@ changelog:
       - "^test:"
 dockers:
   - image_templates:
-      - southclaws/wadsworth:{{ .Tag }}
-      - southclaws/wadsworth:v{{ .Major }}
-      - southclaws/wadsworth:v{{ .Major }}.{{ .Minor }}
-      - southclaws/wadsworth:latest
+      - picostack/picobot:{{ .Tag }}
+      - picostack/picobot:v{{ .Major }}
+      - picostack/picobot:v{{ .Major }}.{{ .Minor }}
+      - picostack/picobot:latest
 nfpms:
   - vendor: Southclaws
-    homepage: https://github.com/Southclaws/wadsworth
+    homepage: https://github.com/picostack/picobot
     maintainer: Southclaws <hello@southcla.ws>
     description: |
       A docker-compose application manager that deploys and maintains a set of

Dockerfile

@@ -1,3 +1,3 @@
 FROM docker/compose
-COPY wadsworth /bin/wadsworth
-ENTRYPOINT ["wadsworth"]
+COPY picobot /bin/picobot
+ENTRYPOINT ["picobot"]

README.md

@@ -1,18 +1,18 @@
-# Wadsworth
+# Picobot
 
-_The [Mister Handy robot][wadsworth] of automation!_
+_The little git robot of automation!_
 
-[![Build Status](https://travis-ci.org/Southclaws/wadsworth.svg?branch=master)](https://travis-ci.org/Southclaws/wadsworth)
+[![Build Status](https://travis-ci.org/picostack/picobot.svg?branch=master)](https://travis-ci.org/picostack/picobot)
 
-Wadsworth is a git-driven task runner to automate the application of configs.
+Picobot is a git-driven task runner to automate the application of configs.
 
 ## Overview
 
-Wadsworth is a little tool for implementing [Git-Ops][git-ops] in single-server environments. It's analogous to
+Picobot is a little tool for implementing [Git-Ops][git-ops] in single-server environments. It's analogous to
 [kube-applier][kube-applier], [Terraform][terraform], [Ansible][ansible] but for automating lone servers that do not
 need cluster-level orchestration.
 
-Instead, Wadsworth aims to be extremely simple. You give it some Git repositories and tell it to run commands when those
+Instead, Picobot aims to be extremely simple. You give it some Git repositories and tell it to run commands when those
 Git repositories receive commits and that's about it. It also provides a way of safely passing in credentials from
 [Hashicorp's Vault][vault].
 
@@ -21,16 +21,16 @@ Git repositories receive commits and that's about it. It also provides a way of
 ### Linux
 
 ```sh
-curl -s https://raw.githubusercontent.com/Southclaws/wadsworth/master/install.sh | bash
+curl -s https://raw.githubusercontent.com/picostack/picobot/master/install.sh | bash
 ```
 
 Or via Docker:
 
 ```sh
-docker pull southclaws/wadsworth:v1
+docker pull picostack/picobot:v1
 ```
 
-See the docker section below and the image on [Docker Hub](https://hub.docker.com/r/southclaws/wadsworth).
+See the docker section below and the image on [Docker Hub](https://hub.docker.com/r/picostack/picobot).
 
 ### Everything Else
 
@@ -39,22 +39,22 @@ Windows/Mac usage is probably just local testing so just use `go get` for these
 
 ## Usage
 
-Currently, Wadsworth has a single command: `run` and it takes a single parameter: a Git URL. This Git URL defines the
-"Config Repo" which contains Wadsworth configuration files. These configuration files declare where Wadsworth can find
-"Target Repos" which are the repos that contain all the stuff you want to automate. The reason Wadsworth is designed
-this way instead of just using the target repos to define what Wadsworth should do is 1. to consolidate Wadsworth config
+Currently, Picobot has a single command: `run` and it takes a single parameter: a Git URL. This Git URL defines the
+"Config Repo" which contains Picobot configuration files. These configuration files declare where Picobot can find
+"Target Repos" which are the repos that contain all the stuff you want to automate. The reason Picobot is designed
+this way instead of just using the target repos to define what Picobot should do is 1. to consolidate Picobot config
 into one place, 2. separate the config of the tools from the applications and 3. keep your target repos clean.
 
-Wadsworth also has a Docker image - see below for docker-specific information.
+Picobot also has a Docker image - see below for docker-specific information.
 
 ### Configuration
 
-The precursor to Wadsworth used JSON for configuration, this was fine for simple tasks but the ability to provide a
+The precursor to Picobot used JSON for configuration, this was fine for simple tasks but the ability to provide a
 little bit of logic and variables for repetitive configurations is very helpful. Inspired by [StackExchange's
-dnscontrol][dnscontrol], Wadsworth uses JavaScript files as configuration. This provides a JSON-like environment with
+dnscontrol][dnscontrol], Picobot uses JavaScript files as configuration. This provides a JSON-like environment with
 the added benefit of conditional logic.
 
-Here's a simple example of a configuration that should exist in the Wadsworth config repo that re-deploys a Docker
+Here's a simple example of a configuration that should exist in the Picobot config repo that re-deploys a Docker
 Compose stack whenever it changes:
 
 ```js
@@ -71,7 +71,7 @@ T({
 
 The `T` function declares a "Target" which is essentially a Git repository. In this example, the repository
 `git@github.com:username/my-docker-compose-project` would contain a `docker-compose.yml` file for some application
-stack. Every time you make a change to this file and push it, Wadsworth will pull the new version and run the command
+stack. Every time you make a change to this file and push it, Picobot will pull the new version and run the command
 defined in the `up` attribute of the target, which is `docker-compose up -d`.
 
 You can put as many target declarations as you want in the config file, and as many config files as you want in the
@@ -129,35 +129,27 @@ This would pass the environment variable `MOUNT_POINT=/data` to the `docker-comp
 have a bunch of compose configs that all mount data to some path on the machine, you then use
 `${MOUNT_POINT}/postgres:/var/lib/postgres/data` as a volume declaration in your `docker-compose.yml`.
 
-[wadsworth]: https://i.imgur.com/RCYbkiq.png
-[git-ops]: https://www.weave.works/blog/gitops-operations-by-pull-request
-[kube-applier]: https://github.com/box/kube-applier
-[terraform]: https://terraform.io
-[ansible]: https://ansible.com
-[vault]: https://vaultproject.io
-[dnscontrol]: https://stackexchange.github.io/dnscontrol/
-
 ## Usage as a Docker Container
 
 See the `docker-compose.yml` file for an example and read below for details.
 
-You can run Wadsworth as a Docker container. If you're using it to deploy Docker containers via compose, this makes the
-most sense. This is quite simple and is best done by writing a Docker Compose configuration for Wadsworth in order to
+You can run Picobot as a Docker container. If you're using it to deploy Docker containers via compose, this makes the
+most sense. This is quite simple and is best done by writing a Docker Compose configuration for Picobot in order to
 bootstrap your deployment.
 
-The Wadsworth image is built on the `docker/compose` image, since most use-cases will use Docker or Compose to deploy
+The Picobot image is built on the `docker/compose` image, since most use-cases will use Docker or Compose to deploy
 services. This means you must mount the Docker API socket into the container, just like Portainer or cAdvisor or any of
 the other Docker tools that also run inside a container.
 
 The socket is located by default at `/var/run/docker.sock` and the `docker/compose` image expects this path too, so you
 just need to add a volume mount to your compose that specifies `/var/run/docker.sock:/var/run/docker.sock`.
 
-Another minor detail you should know is that Wadsworth exposes a `HOSTNAME` variable for the configuration script.
+Another minor detail you should know is that Picobot exposes a `HOSTNAME` variable for the configuration script.
 However, when in a container, this hostname is a randomised string such as `b50fa67783ad`. This means, if your
-configuration performs checks such as `if (HOSTNAME === 'server031')`, this won't work. To resolve this, Wadsworth will
+configuration performs checks such as `if (HOSTNAME === 'server031')`, this won't work. To resolve this, Picobot will
 attempt to read the environment variable `HOSTNAME` and use that instead of using `/etc/hostname`.
 
-This means, you can bootstrap a Wadsworth deployment with only two variables:
+This means, you can bootstrap a Picobot deployment with only two variables:
 
 ```env
 VAULT_TOKEN=abcxyz
@@ -166,7 +158,7 @@ HOSTNAME=server012
 
 ### Docker Compose and `./` in Container Volume Mounts
 
-Another caveat to running Wadsworth in a container to execute `docker-compose` is the container filesystem will not
+Another caveat to running Picobot in a container to execute `docker-compose` is the container filesystem will not
 match the host filesystem paths.
 
 If you mount directories from your repository - a common strategy for versioning configuration - `./` will be expanded
@@ -177,3 +169,13 @@ The solution to this is both `DIRECTORY: "/cache"` and `/cache:/cache`: as long
 exists on the host, Docker compose will expand `./` to the same path as the host and everything will work fine.
 
 This also means your config and target configurations will be persisted on the host's filesystem.
+
+<!-- Links -->
+
+[wadsworth]: https://i.imgur.com/RCYbkiq.png
+[git-ops]: https://www.weave.works/blog/gitops-operations-by-pull-request
+[kube-applier]: https://github.com/box/kube-applier
+[terraform]: https://terraform.io
+[ansible]: https://ansible.com
+[vault]: https://vaultproject.io
+[dnscontrol]: https://stackexchange.github.io/dnscontrol/

docker-compose.yml

@@ -1,6 +1,6 @@
 version: 3
 services:
-  image: southclaws/wadsworth:v1
+  image: picostack/picobot:v1
   environment:
     HOSTNAME: ${HOSTNAME}
     DEBUG: "1"

go.mod

@@ -1,4 +1,4 @@
-module github.com/Southclaws/wadsworth
+module github.com/picostack/picobot
 
 go 1.13
 

go.sum

@@ -29,6 +29,7 @@ github.com/cpuguy83/go-md2man/v2 v2.0.0 h1:EoUDS0afbrsXAZ9YQ9jdu/mZ2sXgT1/2yyNng
 github.com/cpuguy83/go-md2man/v2 v2.0.0/go.mod h1:maD7wRr/U5Z6m/iR4s+kqSMx2CaBsrgA7czyZG/E6dU=
 github.com/creack/pty v1.1.7/go.mod h1:lj5s0c3V2DBrqTV7llrYr5NG6My20zk30Fl46Y7DoTY=
 github.com/davecgh/go-spew v1.1.0/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38=
+github.com/davecgh/go-spew v1.1.1 h1:vj9j/u1bqnvCEfJOwUhtlOARqs3+rkHYY13jYWTU97c=
 github.com/davecgh/go-spew v1.1.1/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38=
 github.com/emirpasic/gods v1.12.0 h1:QAUIPSaCu4G+POclxeqb3F+WPpdKqFGlw36+yOzGlrg=
 github.com/emirpasic/gods v1.12.0/go.mod h1:YfzfFFoVP/catgzJb4IKIqXjX78Ha8FMSDh3ymbK86o=
@@ -139,6 +140,7 @@ github.com/pierrec/lz4 v2.4.1+incompatible h1:mFe7ttWaflA46Mhqh+jUfjp2qTbPYxLB2/
 github.com/pierrec/lz4 v2.4.1+incompatible/go.mod h1:pdkljMzZIN41W+lC3N2tnIh5sFi+IEE17M5jbnwPHcY=
 github.com/pkg/errors v0.8.1 h1:iURUrRGxPUNPdy5/HRSm+Yj6okJ6UtLINN0Q9M4+h3I=
 github.com/pkg/errors v0.8.1/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0=
+github.com/pkg/errors v0.9.1 h1:FEBLx1zS214owpjy7qsBeixbURkuhQAwrK5UwLGTwt4=
 github.com/pkg/errors v0.9.1/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0=
 github.com/pmezard/go-difflib v1.0.0 h1:4DBwDE0NGyQoBHbLQYPwSUPoCMWR5BEzIk/f1lZbAQM=
 github.com/pmezard/go-difflib v1.0.0/go.mod h1:iKH77koFhYxTK1pcRnkKkqfTogsbg7gZNVY4sRDYZ/4=
@@ -168,6 +170,7 @@ github.com/stretchr/objx v0.2.0/go.mod h1:qt09Ya8vawLte6SNmTgCsAVtYtaKzEcn8ATUoH
 github.com/stretchr/testify v1.2.2/go.mod h1:a8OnRcib4nhh0OaRAV+Yts87kKdq0PP7pXfy6kDkUVs=
 github.com/stretchr/testify v1.3.0 h1:TivCn/peBQ7UY8ooIcPgZFpTNSz0Q2U6UrFlUfqbe0Q=
 github.com/stretchr/testify v1.3.0/go.mod h1:M5WIy9Dh21IEIfnGCwXGc5bZfKNJtfHm1UVUgZn+9EI=
+github.com/stretchr/testify v1.4.0 h1:2E4SXV/wtOkTonXsotYi4li6zVWxYlZuYNCXe9XRJyk=
 github.com/stretchr/testify v1.4.0/go.mod h1:j7eGeouHqKxXV5pUuKE4zz7dFj8WfuZ+81PSLYec5m4=
 github.com/tv42/httpunix v0.0.0-20150427012821-b75d8614f926 h1:G3dpKMzFDjgEh2q1Z7zUUtKa8ViPtH+ocF0bE0g00O8=
 github.com/tv42/httpunix v0.0.0-20150427012821-b75d8614f926/go.mod h1:9ESjWnEqriFuLhtthL60Sar/7RFoluCcXsuvEwTV5KM=

install.sh

@@ -6,13 +6,13 @@ set -e
 usage() {
   this=$1
   cat <<EOF
-$this: download go binaries for Southclaws/wadsworth
+$this: download go binaries for picostack/picobot
 
 Usage: $this [-b] bindir [-d] [tag]
   -b sets bindir or installation directory, Defaults to ./bin
   -d turns on debug logging
    [tag] is a tag from
-   https://github.com/Southclaws/wadsworth/releases
+   https://github.com/picostack/picobot/releases
    If tag is missing, then the latest will be used.
 
  Generated by godownloader
@@ -51,7 +51,7 @@ execute() {
   srcdir="${tmpdir}"
   (cd "${tmpdir}" && untar "${TARBALL}")
   test ! -d "${BINDIR}" && install -d "${BINDIR}"
-  for binexe in "wadsworth" ; do
+  for binexe in "picobot" ; do
     if [ "$OS" = "windows" ]; then
       binexe="${binexe}.exe"
     fi
@@ -344,10 +344,10 @@ End of functions from https://github.com/client9/shlib
 ------------------------------------------------------------------------
 EOF
 
-PROJECT_NAME="wadsworth"
-OWNER=Southclaws
-REPO="wadsworth"
-BINARY=wadsworth
+PROJECT_NAME="picobot"
+OWNER=picostack
+REPO="picobot"
+BINARY=picobot
 FORMAT=tar.gz
 OS=$(uname_os)
 ARCH=$(uname_arch)

main.go

@@ -13,7 +13,7 @@ import (
 	"go.uber.org/zap"
 	"go.uber.org/zap/zapcore"
 
-	"github.com/Southclaws/wadsworth/service"
+	"github.com/picostack/picobot/service"
 )
 
 var version = "master"
@@ -41,21 +41,21 @@ func init() {
 func main() {
 	app := cli.NewApp()
 
-	app.Name = "wadsworth"
+	app.Name = "picobot"
 	app.Usage = "A git-driven task automation butler."
-	app.UsageText = `wadsworth [flags] [command]`
+	app.UsageText = `picobot [flags] [command]`
 	app.Version = version
-	app.Description = `Wadsworth is a git-driven task runner to automate the application of configs.`
+	app.Description = `Picobot is a git-driven task runner to automate the application of configs.`
 	app.Author = "Southclaws"
 	app.Email = "hello@southcla.ws"
 
 	app.Commands = []cli.Command{
 		{
 			Name:    "run",
 			Aliases: []string{"r"},
-			Description: `Starts the Wadsworth daemon with the specified target repository. This
-repository should contain one or more configuration files for Wadsworth. When
-this repository has new commits, Wadsworth will automatically reconfigure.`,
+			Description: `Starts the Picobot daemon with the specified target repository. This
+repository should contain one or more configuration files for Picobot. When
+this repository has new commits, Picobot will automatically reconfigure.`,
 			Usage:     "argument `target` specifies Git repository for configuration.",
 			ArgsUsage: "target",
 			Flags: []cli.Flag{

service/config/config.go

@@ -10,7 +10,7 @@ import (
 	"github.com/pkg/errors"
 	"github.com/robertkrimen/otto"
 
-	"github.com/Southclaws/wadsworth/service/task"
+	"github.com/picostack/picobot/service/task"
 )
 
 // State represents a desired system state