claude-backup-cron 0.1.0__tar.gz

claude_backup_cron-0.1.0/.gitignore

@@ -0,0 +1,43 @@
+# Byte-compiled / optimised
+__pycache__/
+*.py[cod]
+*$py.class
+
+# Distribution / packaging
+build/
+dist/
+*.egg-info/
+*.egg
+.eggs/
+wheels/
+pip-wheel-metadata/
+
+# Virtual envs
+.venv/
+venv/
+env/
+
+# Test / coverage
+.pytest_cache/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+.cache/
+.tox/
+.nox/
+
+# Linter / type caches
+.mypy_cache/
+.ruff_cache/
+.pytype/
+
+# Editors
+.idea/
+.vscode/
+*.swp
+*.swo
+.DS_Store
+
+# Tool state (in case the user runs the tool in the repo root)
+state/

claude_backup_cron-0.1.0/CHANGELOG.md

@@ -0,0 +1,42 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+Public API (types exported from `claude_backup_cron`, CLI subcommands,
+config schema keys) follows SemVer. The internal subprocess wrapping of
+`git` / `aws` / `age` / `crontab` is not considered API — their exit
+codes and outputs are passed through as-is.
+
+## [Unreleased]
+
+## [0.1.0] — 2026-04-18
+
+### Added
+
+- Initial public release.
+- `claude-backup-cron run` — idempotent scheduled backup with
+  content-hash change detection.
+- `claude-backup-cron show-config` — print the resolved config.
+- `claude-backup-cron install-cron --schedule` / `uninstall-cron` —
+  manage a single marked block in the user crontab.
+- `claude-backup-cron version`.
+- TOML config schema: `[global]`, `[[sources]]`, `[[destinations]]`
+  with three destination kinds: `git`, `s3`, `local`.
+- Optional age encryption per destination via `encrypt_to = "age1..."`.
+- Webhook alerting on failure (Discord/Slack shape-compatible).
+- Deterministic tarball output (mtime / uid / gid zeroed) — identical
+  source trees produce identical backup bytes.
+- Per-destination retry policy: one destination failing does not block
+  the others.
+- Dry-run (`--dry-run`) and JSON (`--json`) output modes.
+- Typed Python library API (`py.typed`): `Config`, `SourceSpec`,
+  `DestinationSpec`, `RunReport`, `StepResult`, `Artefact`, `Upload`,
+  `load`, `run`.
+- CI matrix: Python 3.10/3.11/3.12/3.13 × Linux/macOS/Windows.
+- CodeQL analysis, Dependabot updates, Trusted Publishing to PyPI.
+
+[Unreleased]: https://github.com/hinanohart/claude-backup-cron/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/hinanohart/claude-backup-cron/releases/tag/v0.1.0

claude_backup_cron-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Support. While redistributing the Work or
+      Derivative Works thereof, You may choose to offer, and charge a
+      fee for, acceptance of support, warranty, indemnity, or other
+      liability obligations and/or rights consistent with this License.
+      However, in accepting such obligations, You may act only on Your
+      own behalf and on Your sole responsibility, not on behalf of any
+      other Contributor, and only if You agree to indemnify, defend,
+      and hold each Contributor harmless for any liability incurred by,
+      or claims asserted against, such Contributor by reason of your
+      accepting any such warranty or support.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Hinano Hart
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied. See the License for the specific language governing
+   permissions and limitations under the License.

claude_backup_cron-0.1.0/NOTICE

@@ -0,0 +1,17 @@
+claude-backup-cron
+Copyright 2026 Hinano Hart
+
+This product contains no third-party source code. Runtime shells out to
+the following external binaries when their corresponding features are
+used:
+
+  * git  (https://git-scm.com/) — for the "git" destination kind.
+  * aws  (https://aws.amazon.com/cli/) — for the "s3" destination kind.
+  * age  (https://age-encryption.org/) — when any destination sets
+    encrypt_to.
+  * crontab — for install-cron / uninstall-cron subcommands.
+
+Each is invoked via subprocess with a fixed argv (no shell). The
+project is not affiliated with Anthropic; "Claude Code" is a product
+name of Anthropic, used here only to describe the tool's typical
+backup target.

claude_backup_cron-0.1.0/PKG-INFO

@@ -0,0 +1,218 @@
+Metadata-Version: 2.4
+Name: claude-backup-cron
+Version: 0.1.0
+Summary: Scheduled encrypted backups for Claude Code memory and similar small directories.
+Project-URL: Homepage, https://github.com/hinanohart/claude-backup-cron
+Project-URL: Documentation, https://github.com/hinanohart/claude-backup-cron#readme
+Project-URL: Issues, https://github.com/hinanohart/claude-backup-cron/issues
+Project-URL: Changelog, https://github.com/hinanohart/claude-backup-cron/blob/main/CHANGELOG.md
+Author-email: Hinano Hart <hinanohart@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: age-encryption,backup,claude-code,cron,scheduled-backup
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: System :: Archiving :: Backup
+Classifier: Topic :: Utilities
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: tomli>=2.0; python_version < '3.11'
+Provides-Extra: dev
+Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: pytest-cov>=5.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.6.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# claude-backup-cron
+
+Scheduled, encrypted backups for small-but-high-value directories —
+Claude Code's `memory/` folder in particular, but anything the shape
+would fit.
+
+## What it does
+
+* Tars each configured source directory into a deterministic artefact.
+* Skips the run entirely if nothing has changed since last time
+  (content hash, not mtime — mtime lies).
+* Optionally encrypts the artefact with [age](https://age-encryption.org/)
+  before it ever reaches a destination.
+* Fans out to one or more destinations — a private git remote, an S3
+  bucket, a spare local drive — with independent success/failure per
+  destination.
+* On any failure, posts a short message to an optional webhook
+  (Discord/Slack shape).
+* Installs itself as a cron job with a one-liner.
+
+Zero runtime dependencies on Python 3.11+; `tomli` backport on 3.10.
+External binaries (`git`, `aws`, `age`, `crontab`) are invoked only
+when the corresponding feature is actually used.
+
+## Why
+
+The existing `memory-backup.sh` that ships in many Claude Code setups
+is ~20 lines of bash: great for one machine, brittle in practice —
+silent on failure, no encryption, single destination, no change
+detection. This package is the "I want it to keep working while I'm
+not watching" version: strict typing, deterministic artefacts,
+structured failures, audit-friendly CLI.
+
+## Install
+
+```bash
+pipx install claude-backup-cron
+```
+
+Or in a venv:
+
+```bash
+python3 -m venv ~/.local/venvs/claude-backup-cron
+~/.local/venvs/claude-backup-cron/bin/pip install claude-backup-cron
+```
+
+See [`docs/INSTALL.md`](docs/INSTALL.md) for setup on each destination
+kind (git remote, S3 bucket, local path).
+
+## Configure
+
+Default config location: `~/.config/claude-backup-cron/config.toml`.
+Override with `$CLAUDE_BACKUP_CRON_CONFIG`.
+
+Minimal example:
+
+```toml
+[global]
+alert_webhook = "https://discord.com/api/webhooks/..."
+
+[[sources]]
+id = "claude-memory"
+path = "~/.claude/projects/-home-runza/memory"
+exclude = [".git/*", "*.swp"]
+
+[[destinations]]
+id = "offsite-git"
+kind = "git"
+remote = "git@github.com:me/claude-memory-backup.git"
+branch = "main"
+encrypt_to = "age1abc..."   # omit to upload plaintext
+```
+
+Verify it parses:
+
+```bash
+claude-backup-cron show-config
+```
+
+A fuller example covering all three destination kinds lives in
+[`examples/config.toml`](examples/config.toml).
+
+## Run
+
+```bash
+claude-backup-cron run              # do the thing
+claude-backup-cron run --dry-run    # package sources but don't upload
+claude-backup-cron run --json       # machine-readable report on stdout
+```
+
+Exit codes:
+
+| Code | Meaning                                                      |
+|------|--------------------------------------------------------------|
+| 0    | All steps succeeded (or nothing to do).                      |
+| 2    | At least one source→destination step failed. Others may have succeeded. |
+| 3    | Config or encryption setup error — nothing was uploaded.     |
+
+## Schedule
+
+```bash
+claude-backup-cron install-cron --schedule "0 3 * * *"   # daily 03:00
+claude-backup-cron uninstall-cron
+```
+
+The installer manages a single block in your user crontab, marked
+with `# claude-backup-cron managed entry`. Re-running `install-cron`
+replaces the previous block in place.
+
+## Encryption
+
+Set `encrypt_to = "age1..."` on a destination. The artefact is piped
+through `age --recipient <...>` before upload. We refuse to fall back
+to plaintext on encryption failure — that's exactly the degradation
+you don't want in a backup tool.
+
+To decrypt later:
+
+```bash
+age --decrypt -i ~/.ssh/my-age-key claude-memory-abc123.tar.age \
+  | tar -xvf -
+```
+
+## Library API
+
+```python
+from claude_backup_cron import load, run
+
+config = load()
+report = run(config, dry_run=False)
+if not report.ok:
+    for failure in report.failed:
+        print(failure.source_id, "→", failure.destination_id, failure.message)
+```
+
+All public types are frozen dataclasses (`Config`, `SourceSpec`,
+`DestinationSpec`, `RunReport`, `StepResult`, `Artefact`, `Upload`).
+Typed Python (`py.typed`); passes `mypy --strict`.
+
+## Design commitments
+
+* **Never silently downgrade encryption.** If `encrypt_to` is set and
+  `age` is missing, the destination fails — it does not upload
+  plaintext.
+* **Independent destination failures.** A dead S3 bucket must not
+  prevent the git push that follows.
+* **Deterministic artefacts.** The same tree produces the same tarball
+  bytes (mtime/uid/gid zeroed) so destinations can no-op when nothing
+  has changed.
+* **Zero telemetry.** No phone-home, no metrics. A backup tool that
+  beacons is a backup tool that will be firewalled off.
+
+## Picking a destination kind
+
+Quick rule of thumb:
+
+| Kind    | Good for                                             | Avoid when                                          |
+|---------|------------------------------------------------------|-----------------------------------------------------|
+| `git`   | Small sources (< ~100 MB), full version history matters | The source is large and churns; every run adds a blob to `.git/objects` that is never deleted. |
+| `s3`    | Offsite durability with a lifecycle rule for rotation | You don't have (or don't want) an AWS-shaped account. |
+| `local` | Spare drive, second machine on LAN, bounded retention (`retain = N`) | You need the backup to survive the laptop being stolen. |
+
+Mix and match — having one `git` destination for history and one
+`local` destination for recent rollback is a common shape.
+
+## Threat model & non-goals
+
+* **In scope**: accidental data loss (mistaken `rm`, disk failure, lost
+  laptop, revoked cloud account). The remote copies let you rebuild.
+* **Out of scope**: targeted attack by someone with root on the host.
+  If the attacker can read your config and your age identity file,
+  they can already read your unencrypted source — this is a backup
+  tool, not a sealing room.
+* **Out of scope**: real-time sync. The minimum meaningful schedule is
+  whatever cron runs; continuous replication is a different product.
+
+See [`SECURITY.md`](SECURITY.md) for the vulnerability reporting
+process.
+
+## License
+
+Apache-2.0. See [`LICENSE`](LICENSE) and [`NOTICE`](NOTICE).