A cross-platform deployment utility that packages .NET projects as ready-to-ship installation files in a single step.
PupNet Deploy is a command-line tool that automates the packaging of .NET applications into native installation formats for Linux and Windows. It solves the problem of creating platform-specific distributables (like AppImages, DEB/RPM packages, and Windows Setup files) by providing a unified configuration and build process, removing the need for manual scripting.
.NET developers, particularly those using Avalonia UI for cross-platform GUI applications, who need to distribute their software as native installers for end-users on Linux and Windows systems.
Developers choose PupNet Deploy because it dramatically simplifies the deployment process, replacing complex, error-prone packaging scripts with a single configuration file and command. It supports a wide range of output formats and handles platform-specific details like desktop integration automatically.
PupNet Deploy is a cross-platform deployment utility which packages your .NET project as a ready-to-ship installation file in a single step.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates AppImage, Flatpak, DEB, RPM, Windows Setup, and ZIP files from a single configuration file, eliminating the need for separate packaging scripts for each format, as highlighted in the 'Multi-Format Packaging' feature.
Uses a single `pupnet.conf` file to define all deployment parameters, avoiding manual creation of complex RPM spec or Debian control files, which simplifies the setup process.
Handles Linux desktop entries (.desktop files), icons, and AppStream metadata automatically, ensuring software center compatibility without extra scripting, as detailed in the 'Desktop Integration' section.
Supports custom post-publish scripts for additional file manipulation or adapting to non-.NET projects, demonstrated in the Hello World demo with bash and batch scripts.
Requires separate installation of platform-specific tools like appimagetool, InnoSetup, and flatpak-builder, adding setup complexity and potential version conflicts, as noted in the 'Install & Prerequisites' section.
Version 1.9 introduced a breaking change by requiring external appimagetool, and the README admits issues like package naming inconsistencies and removal problems in Gnome Software Center, indicating ongoing maintenance challenges.
Designed for single applications per package and not suitable for deploying suites, with limitations for terminal applications in Flatpak, as stated in the 'Single App per Install Package' principle and terminal app notes.