If we defined a sbt task, and start it with piaas app run -t. The sbt command will connect to incorrect tty and wait indefinitely. However, if we omit the -t flag, the sbt command can successfully run in the background.

Maybe we should fork a child to run the task ? We could terminate the forked child right after the task was executed, and tail from the main process.

Not sure whether sbt is the sole instance of such issue

Take Angular for example, using a remote machine to serve means we will have to run ng serve in the background. The process should not be terminated even if we closed the ssh session for whatever reason.

The application must redirect log to a file for issue investigation.

.piaas.d, where pid and logs are kept, should be moved out of source directory for the following reasons:

1. They are not exactly source codes.
2. They may be wiped out by sync unless excluded in the ignore file.

I stumbled upon an interesting use case. I synced from my Macbook to a Windows VM. However, I find myself wanted to sync from this windows VM to a second location. The windows VM require wsl rsync to work, but my host doesn't. Obviously, a single executable section in the top-most level of piaasconfig.yml is not enough. The scenario looks like the below:

Host ---> Windows ---> 2nd Windows

It would be nice if we can override executable per profile.

rsync can benefit from an alternative remote shell, like for example using a control master ssh connection.

We should allow user to specify remoteShell under profiles > connection. This will be used as the -e parameter when invoking rsync. For example:

rsync -av -e '{{remoteShell}}' --exclude-from=.piaasignore --delete --copy-links . [email protected]:~/src

Control Master SSH Scenario:

1. We could have opened a control master connection with ssh -nNf -o ControlMaster=yes -o ControlPath="$HOME/.ssh/.control-%L-%r@%h:%p" user@host
2. Specify remoteShell as ssh -o 'ControlPath=$HOME/.ssh/control-%L-%r@%h:%p'
3. The control master connection can be terminated with ssh -O exit -o ControlPath="$HOME/.ssh/.control-%L-%r@%h:%p" user@host

At the moment, we're publishing to gh-pages branch. But github has advised us to use releases.

Github releases involves calling REST API, which I don't feel reasonable to operate by hand. We should use command line tools like this

If the pid is no longer valid, it should show stopped. Therefore allow the app to be restarted.

We may add a toggle to allow searching for process that are child of the reported pid.

See https://github.com/mitchellh/go-ps which reads /proc/stat file for process information.

The current app run / stop / log sub command should be promoted to top command.

• run -> up
• stop -> down
• log -> log

We should better merge the chunks otherwise rsync will be invoked too many times.

Preferably detecting the length of channel and pick them all from the channel.