Overhaul install / bootstrapping, github-based standard install about gopherbot HOT 4 CLOSED

Done so far:

• Robot bootstrap.py plugin init starts a pipeline that will clone a repo for an existing robot, and restarts

Still to do:

• The init pipeline should also run any .gopherci/pipeline.sh|py|rb, to e.g. build loadable go modules (make Clu do this)
• Need a new "state" plugin back backing up and restoring $GOPHER_HOME/state, the bootstrap pipeline creates $GOPHER_HOME/.restore which should trigger an automatic restore (and removal of that file)
• The setup plugin needs an init pipeline that runs when no GOPHER_ENCRYPTION_KEY or GOPHER_CUSTOM_REPOSITORY is set, and there's no $GOPHER_CONFIGDIR/conf/gopherbot.yaml
  • Copy contents of robot.skel to $GOPHER_CONFIGDIR
  • Write GOPHER_PROTOCOL=terminal to .env
  • Restart to run the setup plugin in terminal mode

from gopherbot.

• Generate ssh key pair
• Add admin user
• save-config job
• Default custom/.robot-state -> indicates state repo is in robot-state branch
• Update backup job to check for $GOPHER_CONFIGDIR/.robot-state
• Update restore job to check for $GOPHER_CONFIGDIR/.robot-state
• Update save job to use $(git remote get-url origin) when .git already exists
• Check update job to verify it prefers get-url origin also when .git present
• modify update.sh plugin to include commands for backup, restore and save
• rewrite "update" job in bash

from gopherbot.

Generate THREE ssh keypairs:

• Deploy key - read-only, include flattened private in .env, public in ssh/deploy_rsa.pub
• Manage key - encrypted read-write deploy key the robot uses for read-write access to it's own repository
• Robot key - encrypted (default same passphrase) key the robot uses for all other work

from gopherbot.

Closed by recent merges from parsley42/gopherbot

from gopherbot.