digital-ocean-dynamic-dns 1.3.10

Python-based CLI tool for managing dynamic dns with Digital Ocean.

digital-ocean-dynamic-dns

Dynamic DNS python tool for Digital Ocean

This project offers a way to manage dynamic DNS, with specific support for DigitalOcean authoritative DNS servers.

Example:

1. I own the domain nivin.tech
2. DigitalOcean is my authoritative name server provider for the nivin.tech domain.
3. I use this package (installed as a command line utility and deployed on a device on my home network) to update the DNS records for nivin.tech to point at my home gateway, which is assigned a dynamic IP address by my internet service provider (ISP).

Documentation

Full docs — installation, first-run setup, the complete command reference, and troubleshooting — live under docs/. These are repo-relative links: they render correctly on GitHub, but not from PyPI's rendered long description (this README) — see nivintw/ddns#38 to switch to absolute links once this content actually exists on main (converting now would 404 until this very PR merges):

• Getting Started — install, configure, onboard your first domain
• Commands — every do_ddns subcommand and flag
• Concepts — the domain/subdomain/manage/catalog vocabulary
• Configuration — env vars, file locations, platform limits
• Troubleshooting — common errors and fixes
• Roadmap — known limitations and planned work

This project carries the shared quality baseline: prek hooks (git hygiene, gitleaks, typos, rumdl, SPDX/REUSE headers, ruff, ty) that run identically locally and in CI. Conventional Commits are enforced at commit-msg time (.cz.toml); releases on main are managed by release-please (a Release PR → vX.Y.Z tag + GitHub Release on merge).

Installation

See Getting Started for install instructions (pipx or uv).

Publishing to PyPI

Every GitHub Release triggers a publish workflow (.github/workflows/publish.yml) that builds once, publishes to TestPyPI first (install + import the built wheel as a smoke test), then — gated on that — publishes to PyPI. Auth is OIDC Trusted Publishing (no long-lived secret), bound to two GitHub deployment environments — testpypi and pypi — each restricted to v* tag deployments. This only actually publishes once the one-time setup below is complete — until then, the workflow runs and fails at the TestPyPI step.

One-time setup before the first release:

1. Create the testpypi and pypi environments (repo Settings → Environments), each with a deployment branch/tag policy restricted to v* tags.
2. Add a pending Trusted Publisher on test.pypi.org and pypi.org, each pointing at owner nivintw, repo ddns, workflow publish.yml, and the matching environment (testpypi / pypi).

Until both publishers exist, uv publish fails loudly rather than silently skipping.

License

MIT — and REUSE-compliant.