Installer vault-cli avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt
• Page du gestionnaire de paquets

Commandes et alias

• vlt

Historique du projet

Apache Jackrabbit FileVault entered the Apache Jackrabbit project as a donated repository-content synchronization tool. The Jackrabbit news archive records FileVault 3.0.0 as the first release of the recently donated tool in September 2013, and the release notes identify version 3.0.0 as the initial version of the contribution to Apache Jackrabbit, with the improvement ticket noting Adobe's FileVault contribution to the ASF.

The project then became part of the Apache Jackrabbit ecosystem around JCR, Oak, Sling, and content packages. The official FileVault page describes it as an Apache Software Foundation project and presents the CLI, API, and content-package tooling as pieces of the same repository-to-filesystem mapping system.

Historique d'adoption

FileVault is most visible in Adobe Experience Manager and Apache Jackrabbit/Sling development workflows, where repository content has to move between a running JCR repository and source-controlled project files. Adobe's AEM documentation points developers at the VLT tool for synchronizing a FileVault checkout with a local repository, including checkout, status, diff, and commit-style workflows.

Modes d'utilisation

The `vlt` CLI exposes commands such as `checkout`, `status`, `update`, `commit`, `revert`, `diff`, `import`, `export`, `rcp`, and `sync`. It accepts repository credentials, can update `~/.vault/auth.xml`, and can install or control the Vault Sync service for local filesystem and repository synchronization.

In package-manager terms this formula is valuable because it gives non-Maven users the same `vlt` executable used by JCR/AEM developers. Typical users are not managing HashiCorp Vault; they are treating repository nodes as versionable files, exporting/importing content packages, or bridging a local IDE checkout with a running content repository.

Pourquoi les passionnés de paquets s'y intéressent

The name is easy to confuse with HashiCorp Vault, but the executable `vlt` and the Apache Jackrabbit coordinates make it a Java content-repository tool. Its niche is narrow, yet important for teams that package CMS or JCR repository content as deployable artifacts.

Chronologie

• 2013-09: Apache Jackrabbit FileVault 3.0.0 is released as the first release of the recently donated repository content synchronization tool.
• 2017: Apache Jackrabbit FileVault Package Maven Plugin 1.0.0 is released for content-package builds.
• 2026: Official FileVault documentation is published for version 4.2.0.

Related projects

• Apache Jackrabbit and Jackrabbit Oak provide the surrounding JCR ecosystem.
• Apache Sling and Adobe Experience Manager are common environments where FileVault/VLT workflows appear.
• The FileVault Package Maven Plugin complements `vlt` by building deployable content package artifacts.

Sources

• Adobe AEM VLT tool guide: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/devtools/ht-vlttool
• Apache FileVault release notes: https://github.com/apache/jackrabbit-filevault/blob/master/RELEASE-NOTES.txt
• Apache Jackrabbit news archive: https://jackrabbit.apache.org/jcr/news-archive.html
• Official FileVault page: https://jackrabbit.apache.org/filevault/
• Official VLT usage guide: https://jackrabbit.apache.org/filevault/usage.html