uptoc mit Homebrew installieren

Projektlinks

• Homepage

Befehle und Aliase

• uptoc

Projektgeschichte

The upstream GitHub repository metadata dates the public repository to 2019. The README is primarily operational rather than historical, but it documents the project's focus on deployment drivers for Aliyun OSS, Tencent COS, Qiniu Kodo, Google Storage, and AWS S3.

Adoptionsgeschichte

The README advertises distribution through a Homebrew tap, the main Homebrew formula, deb/rpm release packages, an install script, and manually downloaded release binaries. The batch input lists Homebrew as the package-manager presence for this formula.

Wie es verwendet wird

Typical use is a single `uptoc` invocation with a driver, region, bucket, credentials, and a local distribution directory. The README also documents environment variables for access keys and a GitHub Actions workflow form, making it useful for static-site and CI deployment pipelines.

Warum Paket-Nerds sich dafür interessieren

For package maintainers, Uptoc is a small example of the static-site deployment CLI category: a single binary, cloud-provider matrix, Homebrew formula, release artifacts, and optional GitHub Actions integration.

Zeitleiste

• 2019: Public GitHub repository metadata records repository creation.
• README era: Documented support for OSS, COS, Kodo, Google Storage, and S3.
• README era: Documented installation through Homebrew, deb/rpm packages, shell installer, and release binaries.

Related projects

• The README positions Uptoc alongside provider-specific object-storage CLIs by wrapping several storage backends behind one deployment command.

Quellen

• https://github.com/bonaysoft/uptoc
• https://github.com/bonaysoft/uptoc/blob/master/README.md
• input source_facts.package-manager