lnp-devopscli 2.0.1

DevOps CLI — workspace sync (GDrive, git, GPG, systemd timers) + GitLab/Bitwarden tooling

lnp-devopscli

DevOps CLI for workspace sync (Google Drive + git + GPG + systemd timers) and GitLab/Bitwarden tooling.

Install

Via PyPI (recommended)

pipx install lnp-devopscli
# or
pip install --user lnp-devopscli

Provides two equivalent commands: devopscli and dc.

From source

git clone https://gitlab.com/lnp-consulting-ti/devops/devops-cli.git ~/bin/devops-cli
cd ~/bin/devops-cli && make setup

Bootstrap on a new PC

For a full workspace bootstrap (rclone + GPG + git-crypt + 10 repos + systemd timers), use the public bootstrap launcher:

bash <(curl -fsSL https://gitlab.com/-/snippets/6003334/raw/main/bootstrap.sh)

See MIGRATION-RUNBOOK.md for the complete migration procedure.

Commands

devopscli ws sync             # full bidirectional sync (pull → git → push)
devopscli ws push             # sync local → GDrive (13 categories)
devopscli ws pull             # sync GDrive → local
devopscli ws doctor           # health check (deps, configs, timers, repos)
devopscli ws ai-sync          # git pull/commit/push for ai_workspaces
devopscli ws repos-sync       # git pull/commit/push for repos_sync
devopscli ws gpg-backup       # export GPG key + encrypt + send to GDrive
devopscli ws gpg-restore      # download GPG key from GDrive + decrypt + import
devopscli ws install-timers   # install systemd user timers (replaces cron)
devopscli ws uninstall-timers # remove systemd timers

See devopscli ws --help for the full list.

Security

The CLI is open source but never accesses your data without your credentials:

• Google OAuth protects access to your GDrive (rclone config)
• GPG passphrase protects the GPG key backup
• git-crypt protects .env files inside synced repos
• GitLab/SSH keys protect access to private repositories

Anyone can pip install the CLI — but without your credentials, they cannot access your data.

Configuration

Edit ~/bin/config.yaml (synced via ws push step 7):

ai_workspaces:
  - name: "workspace-personal"
    path: "~/workspace-personal"
    clone_url: "[e-mail]:user/repo.git"
    remote: "origin"
    branch: "main"
    auto_commit: true
    commit_message: "chore(auto-sync): snapshot via ws ai-sync"

repos_sync:
  - name: "devops-cli"
    path: "~/bin/devops-cli"
    clone_url: "[e-mail]:lnp-consulting-ti/devops/devops-cli.git"
    remote: "origin"
    branch: "main"
    auto_commit: true
    commit_message: "chore(auto-sync): snapshot via ws repos-sync"

Release

To publish a new version to PyPI:

# 1. Bump version in pyproject.toml
git commit -am "chore(release): v1.0.1"

# 2. Tag and push
git tag v1.0.1
git push origin main v1.0.1

The GitLab CI pipeline auto-publishes when a tag matches v*.*.*.

Setup once: add PYPI_TOKEN to GitLab CI/CD Variables (Settings > CI/CD).

License

MIT