Make Flask app contact "deploy agent" instead of sudo'ing Flask

[zoidyzoidzoid]

"we were chatting about this today and perhaps reducing the "attack surface" on the flask app by having
it send rpc/something to a "deploy agent" running with the required privileges rather than having the
flask app (running as root) itself do the deploy.

Do we even care about it that much if it's going to be on some arbitrary http(s) port?

Once #71 or someone else writing a Flask app is merged.

[stormf]

what if we made the flask app run as a user that is allowed to sudo /path/to/deploy d <app_name>?

[adrianmoisey]

The current version of the flask app just calls deploy directly: https://github.com/yola/yodeploy/pull/71/files#diff-686cfabcd9f0ce5d0eb95fdf5c94d3dfR39

If we wanted to protect ourselves with sudo we would need to call the process directly.

[stormf]

Right I keep forgetting this. Ignore me.