on AWS the supervisord.conf file is wrong.

[drj11]

As @ilya points out in Trello, the supervisord.conf file also needs templating.

[drj11]

troubleshoot supervisord not starting automatically during provisioning on AWS

[drj11]

Fixed by #937

[hackdna]

Still a problem when running commit 11b9d80. In supervisord.conf only [program:worker1] section contains
environment = PATH="/home/ubuntu/.virtualenvs/refinery-platform/bin". All others contain environment = PATH="/bin".

[drj11]

Yes, the previous PR, #937, still wasn't right.

Now that you've merged that one, I've made another PR which should be right this time. #941

[hackdna]

It's #941, not #940 [oh yes, I've edited that: drj]. I'll merge it and test it.

[drj11]

@ilya did you know that you don't need to merge a branch to test deployment on AWS by the way? (as long as it's a pushed commit; it uses your current commit (from git rev-parse HEAD) as the deploy target).

[hackdna]

Yes, the problem is that you can't easily switch branches if you have uncommitted local changes. What would great is to be able to specify an arbitrary commit as the deploy target.

[drj11]

you can git stash, change branch, deploy, change branch back, git stash pop. but that is long enough to be error prone. In principle what you suggest is doable because all the current thing does is set GIT_BRANCH (see the stack.py script). That could be changed so it was possible to override.