Installer acreom avec Homebrew Cask

Liens du projet

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

Commandes et alias

Aucun alias exécutable n'a été trouvé dans la base locale des paquets.

Historique du projet

acreom was created as a local-first second brain and personal knowledge base for software engineers. The desktop client was published as GPLv3 software using an Electron-based application architecture.

The project grew to combine pages, tasks, daily planning, projects, version history, calendar features, encrypted synchronization, and integrations while retaining Markdown files as the foundation of local vaults.

Historique d'adoption

acreom developed as a cross-platform, local-first knowledge base aimed particularly at software engineers. Its public desktop application repository and GPLv3 license enabled users to inspect, build, and contribute to the client.

The product expanded beyond local Markdown vaults with optional end-to-end encrypted cloud synchronization, mobile access, sharing, calendars, and integrations with developer tools including Jira, GitHub, and Linear.

Modes d'utilisation

Users create a vault and choose its directory; acreom stores pages there as plain-text Markdown. Vaults can remain completely local and offline or enable acreom Cloud for synchronization, integrations, backup, mobile use, and web access.

Typical workflows include daily stand-up notes, agendas, project organization, issue tracking, task management, technical documentation, and searchable personal knowledge. Existing Markdown directories can be imported by selecting them as a vault.

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

acreom appeals to users who want modern project and daily-note workflows without surrendering plain-text ownership. User-selected Markdown vaults make the important data portable and inspectable, while the open Electron client provides a self-build path.

Its mix of local-first storage, optional encrypted services, developer-focused integrations, and Homebrew cask distribution places it in the same package culture as hackable Markdown knowledge bases and developer notebooks.

Chronologie

• Early development: acreom launched as a local-first knowledge base for developers.
• Version 1.14.0 era: New synchronized accounts began using end-to-end encryption by default.
• Later development: The application added project views, mobile clients, sharing, calendars, and developer-service integrations.
• Current project: The desktop client is maintained publicly under the GPLv3 license.

Related projects

• Markdown: the plain-text storage format used for acreom pages.
• Electron: the desktop application platform used by the open-source client.
• Jira, GitHub, and Linear: developer services supported by acreom integrations.

Sources

• Official encryption documentation: https://acreom.com/docs/encryption
• Official pages documentation: https://acreom.com/docs/pages
• Official repository and README: https://github.com/Acreom/app
• Official vault documentation: https://acreom.com/docs/create-vault