added new install_pipelines_and_steps() method and we now store a Manager on ourselves so we can handle register_farm_server(); both methods help vrpipe-server manage setups
moved trigger-related stuff from Manager to PipelineSetup, which can now do what Manager spool() used to do for all or a single dataelement; Manager gains register_farm_server() method so vrpipe-server can get a FarmServer instance; PipelineSetup gains desired_farm and controlling_farm attributes so vrpipe-server can (via FarmServer) claim the setups it is controlling
steps() no longer initiates a _constuct_pipeline; this now only occurs via BackEnd->install_pipelines_and_steps()
added question and handling for choosing what farm the setup should run from
new --farm mode which initiates pipelinesetup management; still in the middle of implementing this, currently only does the "trigger" side of things
new FarmServer table so that vrpipe-server can keep track of if it should be managing setups, and what setups it should manage
Merge branch 'develop' of /software/vertres/git/origin/vr-pipe into feature/hive
merge from develop, resolving conflicts
reverted some white space changes back to develop version
pull from develop, resolving conflicts
pull from develop, resolving conflicts
Merge branch 'develop' of /software/vertres/git/origin/vr-pipe into feature/hive
Merge branch 'develop' of /software/vertres/git/origin/vr-pipe into feature/hive
BackEnd->log() can now be used to send emails to users and admin
initial very limited tests for the BackEnd module
Merge branch 'develop' of /software/vertres/git/origin/vr-pipe into feature/hive
merge from develop, resolving conflicts
merge from develop, resolving conflicts
in start/stop messages, now make clear the deployment
restart the testing server at start of tests, in case server using old code is still running