Closed sam-github closed 9 years ago
After talking with @rmg, Decided that this change is not necessary.
Using STRONGLOOP_PM env for strong deploy does not work since this can point to a socket file which would not accept git/tar deployments.
On the mesh side, it makes sense to include deploy s a sub commands of meshctl along with other commands which allow listing, checking status etc of services
:+1:
Deploy should support the same env variables as slc pmctl and slc schedctl. Also, current WIP of schedctl requires deploying to a long URL... we probably need
slc deploy
to take the service name/number as an argument.