{{define "footleft"}}<a href="/{{.Owner}}/{{.Name}}/runners">runners</a>{{end}}
{{define "body" -}}
<div class="bar">
  <div class="secondary">{{template "crumbs" .}} / <span class="here">add a runner</span></div>
  <div class="muted small">{{.Token}}</div>
</div>
<div class="pane wide">
  <div class="label">paste on any machine you want to build on.</div>
  <div class="label note-wide">linux, macos</div>
  <pre class="box">curl -sL {{.ExternalURL}}/runner.sh | sh -s {{.Token}}</pre>
  <div class="label note-wide">windows</div>
  <pre class="box">irm {{.ExternalURL}}/runner.ps1 | iex; barerepo-runner {{.Token}}</pre>
  <div class="label note-wide">already have the binary</div>
  <pre class="box">barerepo-runner {{.Token}} --labels build,test</pre>
  <div class="muted small stack note-wide">
    <div>the runner dials out. it needs no inbound port and no public address.</div>
    <div>token scopes to this repo. revoke it on your keys page.</div>
    <div>this token is shown once. only its hash is kept.</div>
    <div>the machine remembers this barerepo, so the line above needs no address.</div>
    <div>a runner is a program because it long-polls. the protocol is plain http:</div>
    <div class="secondary">POST /runner/attach &middot; GET /runner/poll &middot; POST /runner/log &middot;
      POST /runner/done &middot; POST /runner/artifact</div>
    <div>write your own if you would rather.</div>
    <div>a build attaches a file to a release with the last one. it is handed
      BAREREPO_URL, BAREREPO_REPO, BAREREPO_JOB and BAREREPO_JOB_TOKEN:</div>
    <pre class="box">curl -X POST "$BAREREPO_URL/runner/artifact" \
  -H "Barerepo-Token: $BAREREPO_JOB_TOKEN" -H "Barerepo-Job: $BAREREPO_JOB" \
  -H "Barerepo-Tag: v1.0.0" -H "Barerepo-File: johnbot-linux-amd64" \
  --data-binary @johnbot-linux-amd64</pre>
  </div>
</div>
{{- end}}