sysup 0.1.0

[![License BSD-2-Clause](https://img.shields.io/badge/License-BSD--2--Clause-blue.svg)](https://opensource.org/licenses/BSD-2-Clause)
[![License MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
[![AppVeyor CI](https://ci.appveyor.com/api/projects/status/github/KizzyCode/Sysup-rust?svg=true)](https://ci.appveyor.com/project/KizzyCode/Sysup-rust)
[![docs.rs](https://docs.rs/sysup/badge.svg)](https://docs.rs/sysup)
[![crates.io](https://img.shields.io/crates/v/sysup.svg)](https://crates.io/crates/sysup)
[![Download numbers](https://img.shields.io/crates/d/sysup.svg)](https://crates.io/crates/sysup)
[![dependency status](https://deps.rs/crate/sysup/latest/status.svg)](https://deps.rs/crate/sysup)


# `sysup`
Welcome to `sysup` 🎉

`sysup` is a small, lightweight aggregator to perform software updates on local and remote systems. It is designed
around modular update steps and can be easily extended with additional or specialized steps.


## Security and Safety
Since `sysup` performs potentially dangerous operations and needs to operate with elevated rights, trust is paramount.

The application is designed to be simple to understand and reasonably auditable, especially also regarding supply-chain
attacks. Update steps are designed to be simple and lightweight, and should not reinvent the wheel. Dependencies will
only be included if they are necessary. Unsafe code is forbidden.

`sysup` is in a very early state of development. It will miss a lot of important steps, and existing steps might be
buggy. Use with caution, and perform your own security and safety assessment if approriate. See also
[LICENSE MIT](LICENSE%20MIT.md) and [LICENSE BSD 2-CLAUSE](LICENSE%20BSD%202-CLAUSE.md).


## Example
```sh
# Invoking sysup:
sysup
```

For an example configuration, see [.sysup.example.conf](.sysup.example.conf).