Tarball generation as an option

[sebas5384]

This deploy workflow is not a perfect fit for all cases. Deploy

• A tarball (sans node_modules/ and .git/) is transferred to /tmp/package.tar.gz
• If it exists, $HOME/tallerwebsolutions_el-tracker.old is deleted.
• If it exists, $HOME/tallerwebsolutions_el-tracker is renamed to $HOME/tallerwebsolutions_el-tracker.old.
• The tarball is extracted into $HOME/tallerwebsolutions_el-tracker for you automatically.

So for example, lets say I want to connect to a remote server via ssh and only execute some commands, like, git pull of the specifically branch being deployed.

What should be the best way to do this?

[kfatehi]

You're right. I think it should be an option -- the stuff you just pasted should be a "Workflow" and there can be one or more "Workflows" (added via Pull Requests).

I think the default workflow should be "Custom" in which that help text is not visible, no tarball is created or transferred, and you end up in the user's home directory at which point commands are executed.

The "Tarball" workflow should be what we have now.

Thoughts ?

[kfatehi]

@sebas5384 this is done in HEAD

[sebas5384]

:+1: