A command-line tool that enables quick build and run deployments over SSH.
:star: Please star this project if you find it useful!
A dotnet
CLI command that enables quick deployments over SSH. This program was specifically designed to streamline .NET application development for the Raspberry Pi running Raspbian.
If you came here looking for our old version of SSHDeploy please click here, otherwise you are in the right place
The following commands are currently available:
dotnet-sshdeploy monitor
- Watches changes on a single file, if this event is raised then it proceeds to send the specified source path files over SSHdotnet-sshdeploy push
- Single-use command that transfers files over SSHWe are using the brand new implementation of the global tool in .NET Core Apps 2.1+. Now you can easily download the package by running the next command
dotnet tool install -g dotnet-sshdeploy
If you download the project and want to test installing your own version of the project you need to pack and then install the nuget
// In the root of your project run
dotnet pack
// Run the following command where you nupkg was created
dotnet tool install -g dotnet-sshdeploy --add-source ./
There are two ways of passing arguments: the old school way using the cli and our approach using the csproj file.
<PropertyGroup>
<SshDeployHost>192.168.2.194</SshDeployHost>
<SshDeployClean />
<SshDeployTargetPath>/home/pi/libfprint-cs</SshDeployTargetPath>
<SshDeployUsername>pi</SshDeployUsername>
<SshDeployPassword>raspberry</SshDeployPassword>
<RunPostBuildEvent>OnBuildSuccess</RunPostBuildEvent>
</PropertyGroup>
<Target Condition="$(BuildingInsideSshDeploy) ==''" Name="PostBuild" AfterTargets="PostBuildEvent">
<Exec Command="cd $(ProjectDir)" />
<Exec Command="dotnet-sshdeploy push" />
</Target>
Voilà! sshdeploy finds the necessary arguments provided using proper xml tags and deploys after a successful build
BuildingInsideSshDeploy
to make sure this event will not be executed within sshdeploy’s build method to avoid an infinite loop#### Monitor
echo %DATE% %TIME% >> "$(TargetDir)sshdeploy.ready"
*This simply writes the date and time to the sshdeploy.ready
file. Whenever this file CHANGES, the deployment tool will perform a deployment.<RemoteHost>192.168.2.194</RemoteHost>
<SourcePath>C:\projects\Unosquare.Labs.RasPiConsole\Unosquare.Labs.RasPiConsole\bin\Debug</SourcePath>
<RemoteTargetPath>/home/pi/libfprint-cs</RemoteTargetPath>
<RemoteUsername>pi</RemoteUsername>
<RemotePassword>raspberry</RemotePassword>
dotnet-sshdeploy monitor
FYI: Arguments passed using the csproj file will not override the ones provided using the cli ### XML Tags Heres a complete list of arguments with their corresponding XML tag.
Args | XML Tag |
---|---|
-m,–monitor | <SshDeployMonitorFile> |
-f,–framework | <TargetFramework> |
-r,–runtime | <RuntimeIdentifier> |
-s, –source | <SshDeploySourcePath> |
-t,–target | <SshDeployTargetPath> |
–pre | <SshDeployPreCommand> |
–post | <SshDeployPostCommand> |
–clean | <SshDeployClean/> |
–exclude | <SshDeployExclude> |
-v,–verbose | <SshDeployVerbose/> |
-h,–host | <SshDeployHost> |
-p,–port | <SshDeployPort> |
-u,–username | <SshDeployUsername> |
-w,–password | <SshDeployPassword> |
-l,–legacy | <SshDeployLegacy/> |
cd C:\projects\Unosquare.Labs.RasPiConsole\Unosquare.Labs.RasPiConsole\
dotnet-sshdeploy push -f netcoreapp2.0 -t "/home/pi/libfprint-cs" -h 192.168.2.194
-f
refers to the source framework-t
refers to the target path-h
refers to the host (IP address of the Raspberry Pi)
* For a detailed list of all the arguments available please see below or execute dotnet-sshdeploy push
The following steps outline a continuous deployment of a Visual Studio solution to a Raspberry Pi running the default Raspbian SSH daemon.
echo %DATE% %TIME% >> "$(TargetDir)sshdeploy.ready"
*This simply writes the date and time to the sshdeploy.ready
file. Whenever this file CHANGES, the deployment tool will perform a deployment.cd "C:\projects\Unosquare.Labs.RasPiConsole\Unosquare.Labs.RasPiConsole\"
dotnet-sshdeploy monitor -s "C:\projects\Unosquare.Labs.RasPiConsole\Unosquare.Labs.RasPiConsole\bin\Debug" -t "/home/pi/target" -h 192.168.2.194 -u pi -w raspberry
-s
refers to the source path of the files to transfer.t
refers to the full path of the target directory.-h
refers to the host (IP address of the Raspberry Pi).-u
refers to the login.-w
refers to the password.
* Note that there are many more arguments you can use. Simply issue
dotnet-sshdeploy monitor
This will get you all the options you can use.
Monitor mode starting Monitor parameters follow: Monitor File C:\projects\Unosquare.Labs.RasPiConsole\Unosquare.Labs.RasPiConsole\bin\Debug\sshdeploy.ready Source Path C:\projects\Unosquare.Labs.RasPiConsole\Unosquare.Labs.RasPiConsole\bin\Debug Excluded Files .ready|.vshost.exe|.vshost.exe.config Target Address 192.168.2.194:22 Username pi Target Path /home/pi/target Clean Target YES Pre Deployment Post Deployment Connecting to host 192.168.2.194:22 via SSH. Connecting to host 192.168.2.194:22 via SFTP. File System Monitor is now running. Writing a new monitor file will trigger a new deployment. Remember: Press Q to quit. Ground Control to Major Tom: Have a nice trip in space!
7. Now go back to your Visual Studio Solution, right click on the project, a select "Rebuild". You should see the output in the command line similar to the following:
Starting deployment ID 1 - Sunday, June 14, 2015 10:16:20 PM
Cleaning Target Path '/home/pi/target'
Deploying 3 files.
Finished deployment in 0.88 seconds. ``` * Every time you rebuild your project, it will be automatically deployed!
In order to make this tool much more useful, we need to take advantage of the pre and post commands. The idea is to find the process and kill it if it is currently running on the pre-command, and run the process once the deployment has been completed using the post-command argument. The hope is that this will make the deploy, run, and debug cycle, much less tedious for a .NET developer using a Raspberry Pi.
Here’s a good example of using pre and post commands to acocmplish the above:
dotnet-sshdeploy monitor -s "C:\projects\libfprint-cs\trunk\Unosquare.Labs.LibFprint.Tests\bin\Debug" -t "/home/pi/libfprint-cs" -h 192.168.2.194 --pre "pgrep -f 'Unosquare.Labs.LibFprint.Tests.exe' | xargs -r kill" --post "mono /home/pi/libfprint-cs/Unosquare.Labs.LibFprint.Tests.exe" --clean False
Short Argument | Long Argument | Description | Default | Required |
---|---|---|---|---|
-m | –monitor | The path to the file used as a signal that the files are ready to be deployed. Once the deploymetn is completed,the file is deleted. | sshdeploy.ready | :heavy_check_mark: |
-s | –source | The source path for the files to transfer | :heavy_check_mark: | |
-t | –target | The target path of the files to transfer | :heavy_check_mark: | |
–pre | Command to execute prior file transfer to target | :x: | ||
–post | Command to execute after file transfer to target | :x: | ||
–clean | Deletes all files and folders on the target before pushing the new files | True | :x: | |
–exclude | a pipe (|) separated list of file suffixes to ignore while deploying. | .ready|.vshost.exe|.vshost.exe.config | :x: | |
-v | –verbose | Add this option to print messages to standard error and standard output streams. | True | :x: |
-h | –host | Hostname or IP Address of the target. – Must be running an SSH server. | :heavy_check_mark: | |
-p | –port | Port on which SSH is running. | 22 | :x: |
-u | –username | The username under which the connection will be established. | pi | :x: |
-w | –password | The password for the given username. | raspberry | :x: |
-l | –legacy | Monitor files using legacy method | False | :x: |
Short Argument | Long Argument | Description | Default | Required |
---|---|---|---|---|
-c | –configuration | Target configuration. | Debug | :x: |
-f | –framework | The source framework | :heavy_check_mark: | |
–pre | Command to execute prior file transfer to target | :x: | ||
–post | Command to execute after file transfer to target | :x: | ||
–clean | Deletes all files and folders on the target before pushing the new files | True | :x: | |
–exclude | a pipe (|) separated list of file suffixes to ignore while deploying. | .ready|.vshost.exe|.vshost.exe.config | :x: | |
-v | –verbose | Add this option to print messages to standard error and standard output streams. | True | :x: |
-h | –host | Hostname or IP Address of the target. – Must be running an SSH server. | :heavy_check_mark: | |
-p | –port | Port on which SSH is running. | 22 | :x: |
-u | –username | The username under which the connection will be established. | pi | :x: |
-w | –password | The password for the given username. | raspberry | :x: |
This code uses the very cool Renci’s SSH.NET library and our awesome SWAN library.