511303 - implement a "deploy" command

Status: RESOLVED FIXED

(Skywriter Graveyard :: General, enhancement, P1)

Description

[Ben Galbraith]

syntax:

deploy [project/path/to/deploy]

the command defaults to the current project's root directory. when executed, the command-line history will prompt for:

Destination URL (e.g., scp://foo.com/bar)
Authorization Type (e.g., username/password, key)
Username
Password

Field names above aren't suggestions for how the UI should label the fields; that should be consistent with VCS form. Also, key mechanism should piggyback on VCS key system.

We probably should also have a:

Delete Existing Contents

field, but that scares me too much.

Comment 1

[Ben Galbraith]

marked as P1 as this is the major feature of the 0.4.3 release

Comment 2

[Kevin Dangoor]

This has been implemented in 0.4.3, with minor changes to the above.

"deploy" has subcommands. The default for "deploy" is "deploy now", which means 
to actually run the deployment. "deploy setup" allows you to change the 
settings for deployment for a given project. "deploy test" allows you to run a 
"dry run" to see what would be copied over, but without actually copying 
anything over.

Rather than destination URL, there is remote host and remote directory. The 
authentication does piggyback on the VCS auth code.

We're using a library called "Omnisync", which attempts to intelligently sync 
files rather than just copying everything over. It has a "delete" option, but 
this is not yet exposed in the UI.