Zongsoft.Tools.Deployer 7.7.7

dotnet tool install --global Zongsoft.Tools.Deployer --version 7.7.7                
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest # if you are setting up this repo
dotnet tool install --local Zongsoft.Tools.Deployer --version 7.7.7                
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=Zongsoft.Tools.Deployer&version=7.7.7                
nuke :add-package Zongsoft.Tools.Deployer --version 7.7.7                

The Zongsoft Deployment Tool

License NuGet Version NuGet Downloads GitHub Stars

README: English | 简体中文


Abstraction

This is an application deployment tool that instructs the deployment tool to copy specific files to the destination location by specifying the deployment file.

It is recommended to define a default deployment file named .deploy in the deployment project directory, and the deployment file is a plain text file in .ini format.

Format Specification

The deployment file is a plain text file in .ini format, and its content consists of Section(Paragraph) and Entry(Entry) enclosed in square brackets, the Section part represents the destination directory of deployment.

The Section and Entry values both support variable references in the format of dollar sign followed by parentheses $(...) or double percent signs %...%, the referenced variable is the deployment options passed in by the command line or environment variables.

Each entry consists of KEY and VALUE parts separated by an equal sign (=), and the VALUE part is optional.

  • The KEY part consists of Parser-Name and Parser-Argument, separated by a colon (:);

    • Parser-Name: If missing, the default path parser is used, except for nuget and delete parsers.
    • Parser-Argument: Parsed by the specified parser, please refer to Parser Argument below for details.
  • The VALUE part consists of Destination and Filtering.

    • Destination: Indicates the destination path for deployment. If missing, the destination directory is specified by the Section, and the destination file name is the same as the source file.
    • Filtering: Indicates the preconditions for parsing, please refer to Filtering below for details.

Parser Argument

Path Parser

Default parser(Unnamed), which means copy the source file indicated by the Parser-Argument to the destination location.

The Parser-Argument represents the path of the source file to be deployed, the source file path supports *, ? and ** wildcards, the ** means multi-level directory matching.

Delete Parser

The parser name is delete or remove, which means delete the specified destination file.

The Parser-Argument represents the destination file to be deleted, and the full path of the destination file is a combination of the directory specified in the Section and the Parser-Argument.

🚨 Note: This parser does not support the Destination part, so this part cannot be defined.

Examples

Delete the Zongsoft.Messaging.Mqtt.option file from the ~/plugins/zongsoft/messaging/mqtt directory in the target location.

[plugins zongsoft messaging mqtt]
nuget:Zongsoft.Messaging.Mqtt
delete:Zongsoft.Messaging.Mqtt.option

💡 Tip: The deployment file in the nuget:Zongsoft.Messaging.Mqtt package in the example contains a default configuration file(i.e. Zongsoft.Messaging.Mqtt.option), but it is not needed in the real project, so the configuration file is removed later.

NuGet Parser

The parser name is: nuget, which means download the NuGet package and perform the deployment, and that the dependencies of the specified package are also downloaded.

The format of Parser-Argument: package@version/path, where @version and /{path} parts are optional.

  • If the version part is unspecified or it is latest, it means the latest version.
  • If the path part is unspecified:
    • If the root directory of the package contains a .deploy file, the deployment file is deployed first;
    • Deploy all files in the lib/{framework} library files directory of the package.

      The {framework} indicates the version of the target framework nearest to the one declared by the $(Framework) variable.

💡 Tip: Zongsoft's NuGet package usually has a deployment file named .deploy in it's root directory, and the artifacts directory in the package includes its plugin files(*.plugin)(required, one or more), configuration files(*.option), the mapping files(*.mapping) for Zongsoft.Data ORM, and other ancillary files.

💡 Note: The variable named NuGet_Server defines the NuGet package source for this parser. If undefined then https://api.nuget.org/v3/index.json is used as its default value.

Examples
  • Get the latest version of the Zongsoft.Plugins NuGet package and deploy the Main.plugin plugin file in it's /plugins directory to the destination ~/plugins directory.

    [plugins]
    nuget:Zongsoft.Plugins/plugins/Main.plugin
    
  • Get the 6.2.0 version of the Zongsoft.Data NuGet package and execute the .deploy deployment file in the package.

    [plugins zongsoft data]
    nuget:Zongsoft.Data@6.2.0
    nuget:Zongsoft.Data@6.2.0/.deploy
    

    Note: Since the root directory of the Zongsoft.Data package contains the .deploy file, the above two writing styles have the same effect.

  • Deploy version 8.3.0 of the MySql. (Assuming the value of the Framework variable is net8.0)

    nuget:MySql.Data@8.3.0
    
    1. First download the MySql.Data@8.3.0 package and its dependencies (ignore dependencies starting with System. and Microsoft.Extensions.):
    BouncyCastle.Cryptography     2.2.1
    Google.Protobuf               3.25.1
    K4os.Compression.LZ4.Streams  1.3.5
    ZstdSharp.Port                0.7.1
    
    1. Get the library files in the above dependency packages that are nearest to the net8.0 Target Framework version specified by the Framework variable.
    2. Copy the library files from the downloaded NuGet package to the destination directory.

Filtering

The part enclosed by < and > at the end of the entry is the filter condition, and entries that do not meet the filter criteria will be ignored.

Multiple conditions are supported. Each condition consists of a variable name and the comparison values, If the variable name starts with !, it means that the matching result of the condition is negated; If you are comparing multiple values, separate them with commas. As follows:

../.deploy/$(scheme)/options/app.$(environment).option       = web.option    <application>
../.deploy/$(scheme)/options/app.$(environment).option       = web.option    <!application>
../.deploy/$(scheme)/options/app.$(environment)-debug.option = web.option    <preview:A,B,C>
../.deploy/$(scheme)/options/app.$(environment)-debug.option = web.option    <!preview:X,Y,Z>
../.deploy/$(scheme)/options/app.$(environment)-debug.option = web.option    <application | debug:on>
../.deploy/$(scheme)/options/app.$(environment)-debug.option = web.option    <!application & !debug:on>
  1. <application> means that there is a variable named application (Regardless of its content), then the result is true.
  2. <!application> means that there is no variable named application (Regardless of its content), then the result is true.
  3. <preview:A,B,C> means that the value of the variable named preview is any one of "A, B, C" (Ignoring case), then The result is true.
  4. <!preview:X,Y,Z> means that the value of the variable named preview is not any one of "X, Y, Z" (Ignoring case), then the result is true.
  5. <application | debug:on> indicates that there is a variable named application (Regardless of its content) OR a variable named debug is on (Ignoring case), the result is true.
  6. <!application & !debug:on> means that there is no variable named application (Regardless of its content) AND the variable named debug is not on(Ignoring case), the result is true.

Supports matching and version comparison of TargetFramework. If TargetFramework ends with ^, it means that the version of the current deployment TargetFramework must be greater than or equal to this version, as follows:

%NUGET_PACKAGES%/mysql.data/8.1.0/lib/netstandard2.1/*.dll     <framework:net7.0^>
%NUGET_PACKAGES%/mysql.data/6.10.9/lib/netstandard2.0/*.dll    <framework:net5.0,net6.0>

Variables

This tool will sequentially load the environment variables, the contents of the appsettings.json file of the deployed application, and the command options for calling this tool into the variable set. If the variable has the same name, the value loaded later will overwrite the value of the variable with the same name loaded before. Note: Variable names are not case sensitive.

NuGet-related parameters can be specified via command options or environment variables:

  • NuGet_Server indicates the NuGet server information, the default value is: https://api.nuget.org/v3/index.json.
  • NuGet_Packages indicates the directory of NuGet packages, the default value is: %USERPROFILE%/.nuget/packages.

Setup

  • List tools
dotnet tool list
dotnet tool list -g
  • Install tool
dotnet tool install -g zongsoft.tools.deployer
  • Upgrade tool
dotnet tool update -g zongsoft.tools.deployer
  • Uninstall tool
dotnet tool uninstall -g zongsoft.tools.deployer

Deploy

  • Execute the default deployment in the host(target) directory:
dotnet deploy -edition:Debug -framework:net8.0
  • If the host(target) directory does not have a default deployment file (.deploy), you must manually specify the deployment file name (multiple deployment files are supported):
dotnet deploy -edition:Debug -framework:net8.0 MyProject1.deploy MyProject2.deploy MyProject3.deploy
  • For the convenience of deployment, you can create a corresponding edition of the deployment script files in the host(target) project, for example:
    • deploy-debug.cmd

      dotnet deploy -edition:Debug -framework:net8.0

    • deploy-release.cmd

      dotnet deploy -edition:Release -framework:net8.0

Command options

  • verbosity option
    • quiet Displays only the necessary output information, usually only error messages.
    • normal Displays warning and error messages, if this command option is not specified, it is the default.
    • detail Displays all output messages, this option can be enabled when troubleshooting.
  • overwrite option
    • alway Always copy and overwrite the destination file.
    • never Copies the destination file only if it does not exist.
    • newest Deploys file copying only if the last modification time of the source file is later than or equal to the last modification time of the destination file. if this command option is not specified, it is the default.
  • destination option

    The specified deployment destination directory. If this command option is not specified, it defaults to the current directory.

NuGet Packages

If the deployment entry is library files in the NuGet package directory, it will preferentially match the library files of the TargetFramework version specified by the Framework variable.

Nearest Matching

Assuming the Framework variable is net9.0, when a deployment file has the following deployment items:

%NUGET_PACKAGES%/mysql.data/8.3.0/lib/net9.0/*.dll

However, the above package library directory does not contains the net9.0 framework version, so the tool will use the library file that is most applicable(nearest) to that framework version. The path will be redirected to:

%NUGET_PACKAGES%/mysql.data/8.3.0/lib/net8.0/*.dll

Others

Reference examples

Product Compatible and additional computed target framework versions.
.NET net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last updated
7.7.7 162 9/1/2024
7.7.0 85 9/1/2024