acme.sh を Homebrew, Nix, apk, apt, pacman でインストール

プロジェクトリンク

• ホームページ
• 上流ドキュメント
• パッケージマネージャページ

コマンドとエイリアス

• acme.sh

プロジェクトの歴史

The GitHub repository was created in December 2015, shortly after Let's Encrypt made ACME-based certificate automation a practical mainstream workflow. The official README describes acme.sh as a full ACME protocol implementation written in Unix shell and tested across Linux, BSDs, macOS, Solaris-family systems, Haiku, and Windows via Cygwin.

The project grew from a Let's Encrypt-oriented client into a general ACME client. Its README lists support for multiple CAs including ZeroSSL, Let's Encrypt, SSL.com, Google Public CA, Actalis, Pebble, and any RFC 8555-compliant CA, while the wiki documents the large DNS API surface used for automated DNS-01 validation.

採用の歴史

acme.sh became a popular package-manager ACME client because it fits shared hosting, appliances, routers, and small servers where a shell-only dependency profile matters. The official README's 'Who Uses acme.sh?' section names deployments and integrations such as FreeBSD.org, Proxmox, pfSense/OPNsense-adjacent tooling, and other hosting/control-panel environments.

The input package-manager facts show acme.sh packaged across Homebrew, Alpine, Debian, Nix, and Arch. The GitHub API reports a large public repository with tens of thousands of stars and thousands of forks, consistent with broad operational adoption.

使われ方

Typical package usage installs the acme.sh command, stores working state under ~/.acme.sh by default, creates a cron renewal job, and issues certificates with webroot, standalone, TLS-ALPN, Apache, Nginx, DNS, DNS alias, stateless, or DNS persist modes. DNS API credentials are exported once and then saved into ~/.acme.sh/account.conf for later renewal runs.

パッケージ好きにとっての重要性

acme.sh matters to package nerds because it is a rare security-critical tool whose portability comes from plain POSIX-ish shell rather than a language runtime. That makes it attractive for Homebrew, distro, appliance, and container packaging, while its large dnsapi collection creates a sprawling map of DNS provider integrations in one scriptable package.

タイムライン

• 2015-12-26: GitHub repository created.
• 2016-04-06: Earliest GitHub release metadata in the current repository lists version 1.2.2.
• 2016-07-02: Version 2.3.0 tag commit appears in the repository tag history.
• 2024: 3.0.x releases continue regular bug-fix and integration work.
• 2026-04-28: Release 3.1.3 published.

Related projects

• Related projects include Let's Encrypt, ZeroSSL, Certbot, Pebble, RFC 8555 ACME servers, and the DNS provider APIs supported by acme.sh's dnsapi wiki.

ソース

• Official README, official wiki, official dnsapi wiki page, GitHub repository/release metadata, and source_facts.package-manager.