/piawg

Primary LanguageRustMozilla Public License 2.0MPL-2.0


piawg

TODO(fnichol): fill in

CI CI Status
Bors enabled
Latest Version Latest version
Documentation Documentation
Crate Downloads Crate downloads
GitHub Downloads Github downloads
Docker Pulls Docker pulls
License Crate license
Table of Contents

CLI

Usage

TODO(fnichol): fill in

For more help and full usage, use the --help or -h flags:

piawg --help

Installation

install.sh (Pre-Built Binaries)

An installer is provided at https://fnichol.github.io/piawg/install.sh which installs a suitable pre-built binary for common systems such as Linux, macOS, Windows, and FreeBSD. It can be downloaded and run locally or piped into a shell interpreter in the "curl-bash" style as shown below. Note that if you're opposed to this idea, feel free to check some of the alternatives below.

To install the latest release for your system into $HOME/bin:

curl -sSf https://fnichol.github.io/piawg/install.sh | sh

When the installer is run as root the installation directory defaults to /usr/local/bin:

curl -sSf https://fnichol.github.io/piawg/install.sh | sudo sh

A nightly release built from HEAD of the main branch is available which can also be installed:

curl -sSf https://fnichol.github.io/piawg/install.sh \
    | sh -s -- --release=nightly

For a full set of options, check out the help usage with:

curl -sSf https://fnichol.github.io/piawg/install.sh | sh -s -- --help

GitHub Releasees (Pre-Built Binaries)

Each release comes with binary artifacts published in GitHub Releases. The install.sh program downloads its artifacts from this location so this serves as a manual alternative. Each artifact ships with MD5 and SHA256 checksums to help verify the artifact on a target system.

Cargo Install

If Rust is installed on your system, then installing with Cargo is straight forward with:

cargo install piawg

From Source

To install from source, you can clone the Git repository, build with Cargo and copy the binary into a destination directory. This will build the project from the latest commit on the main branch, which may not correspond to the latest stable release:

git clone https://github.com/fnichol/piawg.git
cd piawg
cargo build --release
cp ./target/release/piawg /dest/path/

Library

TODO(fnichol): fill in

Usage

This crate is on crates.io and can be used by adding the crate to your dependencies in your project's Cargo.toml file:

[dependencies]
piawg = { version = "0.1.0", default-features = false }

Note that the default features include dependencies which are required to build a CLI and are not needed for the library.

Examples

CI Status

Build (main branch)

Operating System Target Stable Rust
FreeBSD x86_64-unknown-freebsd FreeBSD Build Status
Linux arm-unknown-linux-gnueabihf Linux Build Status
Linux aarch64-unknown-linux-gnu Linux Build Status
Linux i686-unknown-linux-gnu Linux Build Status
Linux i686-unknown-linux-musl Linux Build Status
Linux x86_64-unknown-linux-gnu Linux Build Status
Linux x86_64-unknown-linux-musl Linux Build Status
macOS x86_64-apple-darwin macOS Build Status
Windows x86_64-pc-windows-msvc Windows Build Status

Test (main branch)

Operating System Stable Rust Nightly Rust
FreeBSD FreeBSD Stable Test Status FreeBSD Nightly Test Status
Linux Linux Stable Test Status Linux Nightly Test Status
macOS macOS Stable Test Status macOS Nightly Test Status
Windows Windows Stable Test Status Windows Nightly Test Status

Note: The Minimum Supported Rust Version (MSRV) is also tested and can be viewed in the CI dashboard.

Check (main branch)

Status
Lint Lint Status
Format Format Status

Code of Conduct

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to fnichol@nichol.ca.

Issues

If you have any problems with or questions about this project, please contact us through a GitHub issue.

Contributing

You are invited to contribute to new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.

Release History

See the changelog for a full release history.

Authors

Created and maintained by Fletcher Nichol (fnichol@nichol.ca).

License

Licensed under the Mozilla Public License Version 2.0 (LICENSE.txt).

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the MIT license, shall be licensed as above, without any additional terms or conditions.