How to integrate emplace with my existing dotfiles repository?

Emplace stores its configuration in a .emplace file that can be committed to your dotfiles repo. Use 'emplace config --new' to link it, and the sync will work seamlessly alongside other dotfiles for centralized management.

Emplace vs Ansible: which is better for setting up development machines?

Emplace is lighter and focuses on automatic package tracking across personal machines, while Ansible is more powerful for orchestration and configuration management in teams. Choose Emplace for personal sync, Ansible for complex automation with playbooks.

Does emplace work with Docker or containerized environments?

No, Emplace is designed for host system package managers and doesn't integrate with container runtimes like Docker. For containerized setups, use Dockerfiles or tools like Docker Compose for environment replication.

How does emplace handle package versions?

Emplace tracks the package names as installed but doesn't enforce specific versions. You may need to rely on package manager flags or manual version management to ensure consistency across machines.

Can emplace sync system packages and user packages separately?

It logs packages based on the installation commands used, so system and user packages are tracked together. However, you can manage them manually in the .emplace configuration file if needed.

Emplace or Nix for reproducible environments?

Nix provides fully reproducible, declarative environments with dependency isolation, while Emplace is simpler for syncing existing installations without guarantees. Use Nix for strict reproducibility, Emplace for convenience and cross-manager sync.

Open-Awesome

emplace

AGPL-3.0Rustv1.6.0

A command-line tool that synchronizes installed packages across multiple machines using a version-controlled configuration file.

GitHub

282 stars27 forks0 contributors

What is emplace?

Emplace is a command-line utility that synchronizes installed software packages across multiple computers. It solves the problem of manually replicating development environments by automatically tracking installations from various package managers and allowing users to apply the same set of packages on another machine with a single command.

Target Audience

Developers and system administrators who work across multiple machines (e.g., desktop and laptop, work and home computers) and want to maintain consistent software environments without manual tracking.

Value Proposition

Developers choose Emplace for its extensive package manager support, seamless integration into existing shell workflows, and ability to version-control package lists alongside dotfiles, making environment replication effortless and reproducible.

Overview

👩‍❤️‍💋‍👩 Synchronize installed packages on multiple machines

Use Cases

Best For

Synchronizing software packages between a desktop and a laptop
Setting up a new development machine with the same tools as an existing one
Maintaining consistent package sets across multiple Linux distributions
Tracking installed packages in a version-controlled dotfiles repository
Automating environment replication for team onboarding or disaster recovery
Managing cross-platform tool installations (Linux, macOS, Windows) from a single config

Not Ideal For

Teams requiring deterministic, version-pinned environments like those managed by Nix or Docker Compose
Organizations with centralized IT management needing audit trails and role-based access controls
Users who install software primarily through graphical interfaces or standalone binaries not tracked by supported package managers

Pros & Cons

Pros

Extensive Package Manager Support

Supports over 20 package managers including Apt, Pacman, Homebrew, and Cargo, covering Linux, macOS, and Windows for comprehensive cross-platform synchronization.

Automatic Installation Prompting

After installing a package via a supported manager, it automatically prompts to mirror it in the .emplace file, reducing manual tracking effort.

Git-Integrated Synchronization

Uses Git to version control the .emplace configuration file, enabling automatic push/pull updates and easy sharing across machines.

Shell History Analysis

Can parse shell history files to extract past installation commands, helping sync existing setups retroactively without reinstallation.

Cons

Inactive Core Development

The original developer has stopped active maintenance, relying on community pull requests, which risks slower bug fixes and feature updates.

No Dependency Management

It only tracks package names without handling dependencies or conflicts, potentially causing broken setups when replicating across different machines.

Complex Initial Setup

Requires shell initialization scripts and Git repository configuration, which can be cumbersome for users less familiar with CLI tools and version control.

Frequently Asked Questions

Related Projects

RustDesk

An open-source remote desktop application designed for self-hosting, as an alternative to TeamViewer.

π RuView turns commodity WiFi signals into real-time spatial intelligence, vital sign monitoring, and presence detection — all without a single pixel of video.

Stars85,306

Forks11,380

Last commit21 hours ago

vaultwarden

Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs

Stars64,125

Forks3,026

Last commit3 days ago

Warp

Warp is an agentic development environment, born out of the terminal.

Stars63,607

Forks5,321

Last commit18 hours ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub