dotlayer 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d30157869fd9bd7c0d98d7957fd82879a06db355368ae7a66919d43ba2dac6dc
-  data.tar.gz: 560bf0f69bc6a68083d67739d91a97cbd3f208696313ba97f03619ccbae3901a
+  metadata.gz: 6153afd914718371693784c18c5be35b4f84d2b4ceddda8990efed35e54ad229
+  data.tar.gz: 192e9da8c37c20627151ee35dc415e1ac59eece7e27edb63bb8aac249e0defd7
 SHA512:
-  metadata.gz: ffe27ed4bf4d65aacd1a52fc1c7697771f53b1fe69b1622a10a0789a2e01ce698d56ce6f4a485256e9b86faf5b696efe974d32dacfdfc894ddfdeb6540bb26fc
-  data.tar.gz: 919ce9855ebfb9a7a5ba0b74c06d818f405bf843ba7505433f3529a89dc6565a5f6a04e5f8bf03853fb45f625b964b19c3e2a8686821f5fced95b7e952f2294d
+  metadata.gz: 401aa858f83b8f064b9c6fdf39e2621ce2c4ba53f6fa9ae2ba3e9922b7d74ea20a4bf8ab1b247f4515060d2c051ce4e89b9b7c26288e3a07e3fd581b7550f579
+  data.tar.gz: 6a5aa5a51170cbe973c30854f45b9e1713799cfc8d4d451e058e4a66998390f86eb656c183eda3d99baf95b2334af319cb4ae850f43e593047447e090b1115f8

data/README.md

@@ -13,7 +13,7 @@ config-macos/               → stowed on macOS
 config-omarchy/             → stowed when Omarchy is detected
 config-omarchy-desktop/     → stowed on Omarchy + desktop profile
 config-omarchy-laptop/      → stowed on Omarchy + laptop profile
-config-doximity/            → stowed when doximity group is detected
+config-mycompany/            → stowed when mycompany group is detected
 ```
 
 No config file needed — just name your directories and dotlayer figures out the rest.
@@ -64,7 +64,7 @@ Dotlayer auto-detects four things about your system:
 | **OS** | `RbConfig::CONFIG["host_os"]` | `linux`, `macos` |
 | **Profile** | `hostnamectl chassis` or `$DOTLAYER_PROFILE` | `desktop`, `laptop` |
 | **Distro** | Shell commands from config | `omarchy`, `fedora` |
-| **Group** | Shell commands from config | `doximity`, `acme` |
+| **Group** | Shell commands from config | `work`, `mycompany` |
 
 It then scans your dotfiles repo for directories matching these tags and stows them in layer order:
 
@@ -72,7 +72,7 @@ It then scans your dotfiles repo for directories matching these tags and stows t
 2. **OS layer** — `config-linux` or `config-macos`
 3. **Distro layer** — `config-omarchy`
 4. **Distro + profile** — `config-omarchy-desktop`
-5. **Group layer** — `config-doximity`
+5. **Group layer** — `config-mycompany`
 
 Each layer can add files but never conflict with earlier layers (Stow constraint).
 
@@ -106,8 +106,8 @@ distros:
     detect: . /etc/os-release && test "$ID" = "fedora"
 
 groups:
-  doximity:
-    detect: test -d ~/src/dox
+  mycompany:
+    detect: test -d ~/src/mycompany
 
 system_files:
   - source: config-linux/etc/systemd/system-sleep/xremap-restart.sh
@@ -124,9 +124,35 @@ Config file is discovered automatically from:
 - `~/.public_dotfiles/dotlayer.yml`
 - `~/.dotfiles/dotlayer.yml`
 
-## Multi-repo support
+## Public and private dotfiles
 
-Dotlayer supports multiple repos. Each repo can have its own base packages:
+Most people have two kinds of config: stuff you can share (shell aliases, editor themes, window manager rules) and stuff you can't (API keys, work credentials, employer-specific tooling). Dotlayer handles this with two repos:
+
+```
+~/.public_dotfiles/     ← shared on GitHub, safe for the world to see
+~/.private_dotfiles/    ← private repo (or not pushed at all)
+```
+
+### Why two repos?
+
+A single dotfiles repo forces a choice: keep it private (lose the benefit of sharing) or keep it public (risk leaking secrets). Two repos solves this cleanly:
+
+- **Public repo** — your shell, editor, git, and desktop config. Push to GitHub, share with the community, clone on any new machine.
+- **Private repo** — work-specific config, API tokens, SSH configs, fonts with restrictive licenses, employer tooling. Keep in a private repo or don't push at all.
+
+Both repos stow into the same target (`~`), so your home directory looks the same regardless of which repo a file came from.
+
+### Setting it up
+
+Create both repos:
+
+```sh
+mkdir -p ~/.public_dotfiles ~/.private_dotfiles
+cd ~/.public_dotfiles && git init
+cd ~/.private_dotfiles && git init
+```
+
+Add the dotlayer config at `~/.config/dotlayer/dotlayer.yml`:
 
 ```yaml
 repos:
@@ -138,9 +164,67 @@ repos:
       - fonts
 ```
 
-Repos without any matching base packages automatically stow all their top-level directories (sorted alphabetically). This is useful for private repos that only contain standalone packages.
+The `private: true` flag tells dotlayer which repo to use when you run `dotlayer adopt --private`.
+
+### What goes where?
+
+**Public repo** — uses the standard base packages (`stow`, `bin`, `git`, `zsh`, `config`) with full layering support:
+
+```
+~/.public_dotfiles/
+  config/                       ← shared config (editor, terminal, etc.)
+  config-linux/                 ← Linux-specific overrides
+  config-omarchy/               ← Omarchy distro overrides
+  config-omarchy-desktop/       ← Omarchy + desktop profile
+  git/                          ← git config
+  zsh/                          ← shell config
+  bin/                          ← personal scripts
+  stow/                         ← stow's own config
+```
+
+**Private repo** — can use per-repo packages for layered resolution, plus standalone directories that are all stowed automatically:
+
+```
+~/.private_dotfiles/
+  config/                       ← private config overlays (SSH, API keys)
+  config-mycompany/              ← work-specific config (group layer)
+  fonts/                        ← licensed fonts
+  fonts-linux/                  ← Linux-specific font config
+  claude/                       ← standalone: Claude AI config
+  work/                         ← standalone: work tooling
+  scripts/                      ← standalone: work automation scripts
+```
+
+Directories that match the per-repo base packages (`config`, `fonts`) get full layer resolution. Everything else (`claude`, `work`, `scripts`) is stowed as-is in alphabetical order.
+
+### Adopting files into the right repo
+
+```sh
+# Public config — goes to ~/.public_dotfiles
+dotlayer adopt ~/.config/lazygit config
+
+# Private config — goes to ~/.private_dotfiles
+dotlayer adopt --private ~/.config/lazysql config
+```
+
+### Layer precedence across repos
+
+Repos are processed in order. Public packages are stowed first, then private packages overlay on top. This means:
+
+1. `~/.public_dotfiles/config/` — base config (stowed first)
+2. `~/.public_dotfiles/config-linux/` — OS layer
+3. `~/.public_dotfiles/config-omarchy/` — distro layer
+4. `~/.private_dotfiles/config/` — private overlays (stowed after public)
+5. `~/.private_dotfiles/config-mycompany/` — work group layer
+
+Each layer adds files — they never conflict because different layers use different file paths within the same directory structure.
+
+### Keeping private dotfiles private
+
+Your private repo doesn't need to be pushed anywhere. It works fine as a local-only git repo for tracking changes. If you do want backup:
 
-Repos are processed in order — packages from the first repo are stowed before packages from the second.
+- Push to a **private GitHub/GitLab repo**
+- Use `dotlayer update` to pull both repos at once — it runs `git pull --rebase` on each repo that has a `.git` directory
 
 ## CLI reference
 

data/lib/dotlayer.rb

@@ -1,5 +1,5 @@
 module Dotlayer
-  VERSION = "0.2.0"
+  VERSION = "0.2.1"
 
   autoload :CLI, "dotlayer/cli"
   autoload :Config, "dotlayer/config"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dotlayer
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Douglas Andrade