ocea 2.0.8.dev2__tar.gz

ocea-2.0.8.dev2/.gitignore

@@ -0,0 +1,70 @@
+# Temporary and binary files
+*~
+*.py[cod]
+*.so
+*.cfg
+!.isort.cfg
+!setup.cfg
+*.orig
+*.log
+*.pot
+__pycache__/*
+.cache/*
+.*.swp
+*/.ipynb_checkpoints/*
+.DS_Store
+
+# Project files
+.ropeproject
+.project
+.pydevproject
+.settings
+.idea
+.vscode
+tags
+
+# Package files
+*.egg
+*.eggs/
+.installed.cfg
+*.egg-info
+
+# Unittest and coverage
+htmlcov/*
+.coverage
+.coverage.*
+.tox
+junit*.xml
+coverage.xml
+.pytest_cache/
+
+# Build and docs folder/files
+build/*
+dist/*
+sdist/*
+docs/api/*
+docs/_rst/*
+docs/_build/*
+cover/*
+MANIFEST
+
+# Per-project virtualenvs
+.venv*/
+.conda*/
+.python-version
+# Generated by setuptools_scm
+src/ocea/_version.py
+
+# Environment and secrets
+.env
+.env.*
+
+# Database files
+*.db
+
+# Claude Code
+.claude/
+
+# Build stamps
+.stamps/
+__pycache__/

ocea-2.0.8.dev2/.pre-commit-config.yaml

@@ -0,0 +1,31 @@
+ci:
+  autoupdate_schedule: quarterly
+  autofix_prs: true
+  autofix_commit_msg: "style: auto-fix formatting [pre-commit.ci]"
+
+default_language_version:
+  python: python3.12
+
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.6.9        # pin to a tag; update as needed
+    hooks:
+      - id: ruff
+        args: [--fix]  # Auto-fix without failing
+      - id: ruff-format
+
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.6.0        # pin to a tag; update as needed
+    hooks:
+      - id: check-added-large-files
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+      - id: check-merge-conflict
+
+
+  # If you want Black as well, uncomment this block and keep its rev pinned
+  # - repo: https://github.com/psf/black
+  #   rev: 24.10.0     # example pinned release
+  #   hooks:
+  #     - id: black
+  #       args: ["--line-length=100"]

ocea-2.0.8.dev2/.readthedocs.yml

@@ -0,0 +1,27 @@
+# Read the Docs configuration file
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+# Required
+version: 2
+
+# Build documentation in the docs/ directory with Sphinx
+sphinx:
+  configuration: docs/conf.py
+
+# Build documentation with MkDocs
+#mkdocs:
+#  configuration: mkdocs.yml
+
+# Optionally build your docs in additional formats such as PDF
+formats:
+  - pdf
+
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3.11"
+
+python:
+  install:
+    - requirements: docs/requirements.txt
+    - {path: ., method: pip}

ocea-2.0.8.dev2/AUTHORS.rst

@@ -0,0 +1,5 @@
+============
+Contributors
+============
+
+* Kevin Steptoe <kevin.steptoe@gmail.com>

ocea-2.0.8.dev2/CHANGELOG.rst

@@ -0,0 +1,72 @@
+=========
+Changelog
+=========
+
+Version 2.0.7
+==============
+
+* Always-on spinner and interactive reserved IP selection for ``ocea up``
+* Verify droplet exists in API before acting on stale DB status
+* Fix ``PYTHON_SYS`` fallback to try ``python3`` before Windows-only ``py`` launcher
+
+Version 2.0.6
+==============
+
+* Strip DO auto-generated size/region suffix from droplet names
+
+Version 2.0.5
+==============
+
+* Replace progress line spam with Rich spinners for long waits
+
+Version 2.0.4
+==============
+
+* Fix restore from snapshot ID when DB has old snowballed name
+
+Version 2.0.3
+==============
+
+* Increase IP assignment timeout from 2 to 10 minutes for larger droplets
+
+Version 2.0.2
+==============
+
+* Fix snapshot name snowballing and increase snapshot timeout
+
+Version 2.0.1
+==============
+
+* Fix snapshot lifecycle: wait for completion before destroying droplet
+
+Version 2.0.0
+==============
+
+* Add ``reboot`` command for droplets
+* Refactor ``snap`` command to use subcommands (``snap create``, ``snap list``, ``snap delete``)
+* Add snapshot ID support to ``ocea up`` command
+* Add in-progress snapshot actions to ``list`` command
+* Add cleanup for duplicate archived droplets
+* Refactor ``ocea list`` to show droplets and snapshots with filters
+* Wait for droplet to be active before assigning reserved IP
+* Fix reserved IP not assigned when restoring from snapshot ID
+* Comprehensive database tracking and smart restore
+* Pre-commit CI configuration
+
+Version 1.0.1
+=============
+
+* Added comprehensive database tracking for all operations
+* Added action audit logging
+* Added floating/reserved IP tracking and automatic reassignment
+* Changed ``ocea snap --delete`` to accept multiple snapshot IDs
+* Added ``-h`` help flag to all commands
+
+Version 1.0.0
+=============
+
+* Initial release
+* Commands: list, status, up, down, new, snap
+* Local SQLite database for inventory tracking
+* Support for snapshots and restore operations
+* JSON output for scripting

ocea-2.0.8.dev2/CONTRIBUTING.rst

@@ -0,0 +1,182 @@
+============
+Contributing
+============
+
+Welcome to ``ocea``'s contributor's guide.
+
+This document focuses on getting any potential contributor familiarized
+with the development processes, but `other kinds of contributions`_ are also
+appreciated.
+
+If you are new to using git_ or have never collaborated in a project previously,
+please have a look at `contribution-guide.org`_. Other resources are also
+listed in the excellent `guide created by FreeCodeCamp`_ [#contrib1]_.
+
+Please notice, all users and contributors are expected to be **open,
+considerate, reasonable, and respectful**. When in doubt, `Python Software
+Foundation's Code of Conduct`_ is a good reference in terms of behavior
+guidelines.
+
+
+Issue Reports
+=============
+
+If you experience bugs or general issues with ``ocea``, please have a look
+on the `issue tracker`_. If you don't see anything useful there, please feel
+free to fire an issue report.
+
+.. tip::
+   Please don't forget to include the closed issues in your search.
+   Sometimes a solution was already reported, and the problem is considered
+   **solved**.
+
+New issue reports should include information about your programming environment
+(e.g., operating system, Python version) and steps to reproduce the problem.
+Please try also to simplify the reproduction steps to a very minimal example
+that still illustrates the problem you are facing. By removing other factors,
+you help us to identify the root cause of the issue.
+
+
+Code Contributions
+==================
+
+Submit an issue
+---------------
+
+Before you work on any non-trivial code contribution it's best to first create
+a report in the `issue tracker`_ to start a discussion on the subject.
+This often provides additional considerations and avoids unnecessary work.
+
+Create an environment
+---------------------
+
+Before you start coding, we recommend creating an isolated `virtual
+environment`_ to avoid any problems with your installed Python packages.
+The easiest way is to use the provided Makefile::
+
+    make bootstrap     # Create virtualenv and install dependencies
+    make precommit     # Install pre-commit hooks
+
+Or manually::
+
+    python3 -m venv .venv
+    source .venv/bin/activate
+    pip install -e ".[dev]"
+
+Clone the repository
+--------------------
+
+#. Fork the project repository_: click on the *Fork* button near the top of the
+   page. This creates a copy of the code under your account on GitHub.
+#. Clone this copy to your local disk::
+
+    git clone git@github.com:YourLogin/ocea.git
+    cd ocea
+
+#. Install the project in editable mode with development dependencies::
+
+    pip install -e ".[dev]"
+
+#. Install pre-commit hooks::
+
+    pre-commit install
+
+Implement your changes
+----------------------
+
+#. Create a branch to hold your changes::
+
+    git checkout -b my-feature
+
+   and start making changes. Never work on the main branch!
+
+#. When you're done editing, do::
+
+    git add <MODIFIED FILES>
+    git commit
+
+   to record your changes in git_.
+
+   Please make sure to see the validation messages from ``pre-commit`` and fix
+   any eventual issues. The project uses Ruff_ for linting and formatting.
+
+   .. important:: Don't forget to add unit tests and documentation in case your
+      contribution adds an additional feature and is not just a bugfix.
+
+#. Please check that your changes don't break any unit tests with::
+
+    make test
+
+Submit your contribution
+------------------------
+
+#. If everything works fine, push your local branch to GitHub with::
+
+    git push -u origin my-feature
+
+#. Go to the web page of your fork and click "Create pull request"
+   to send your changes for review.
+
+
+Troubleshooting
+---------------
+
+The following tips can be used when facing problems to build or test the
+package:
+
+#. Make sure to fetch all the tags from the upstream repository_.
+   The command ``git describe --abbrev=0 --tags`` should return the version you
+   are expecting.
+
+#. If you find any problems with missing dependencies, try recreating the
+   virtual environment::
+
+    rm -rf .venv
+    make bootstrap
+
+
+Maintainer tasks
+================
+
+Releases
+--------
+
+If you are part of the group of maintainers and have correct user permissions
+on PyPI_, the following steps can be used to release a new version for
+``ocea``:
+
+#. Make sure all unit tests are successful.
+#. Tag the current commit on the main branch with a release tag, e.g., ``v1.2.3``.
+#. Push the new tag to the upstream repository_, e.g., ``git push upstream v1.2.3``
+#. Clean up the ``dist`` and ``build`` folders with ``tox -e clean``
+   (or ``rm -rf dist build``)
+#. Run ``tox -e build`` and check that the files in ``dist`` have
+   the correct version (no ``.dirty`` or git_ hash) according to the git_ tag.
+#. Run ``tox -e publish -- --repository pypi`` and check that everything was
+   uploaded to PyPI_ correctly.
+
+
+
+.. [#contrib1] Even though, these resources focus on open source projects and
+   communities, the general ideas behind collaborating with other developers
+   to collectively create software are general and can be applied to all sorts
+   of environments, including private companies and proprietary code bases.
+
+
+.. |the repository service| replace:: GitHub
+.. |contribute button| replace:: "Create pull request"
+
+.. _repository: https://github.com/ksteptoe/ocea
+.. _issue tracker: https://github.com/ksteptoe/ocea/issues
+
+
+.. _contribution-guide.org: https://www.contribution-guide.org/
+.. _creating a PR: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
+.. _git: https://git-scm.com
+.. _guide created by FreeCodeCamp: https://github.com/FreeCodeCamp/how-to-contribute-to-open-source
+.. _other kinds of contributions: https://opensource.guide/how-to-contribute
+.. _pre-commit: https://pre-commit.com/
+.. _PyPI: https://pypi.org/
+.. _Python Software Foundation's Code of Conduct: https://www.python.org/psf/conduct/
+.. _Ruff: https://docs.astral.sh/ruff/
+.. _virtual environment: https://realpython.com/python-virtual-environments-a-primer/

ocea-2.0.8.dev2/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2026 Kevin Steptoe
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

ocea-2.0.8.dev2/MANIFEST.in

@@ -0,0 +1,5 @@
+exclude CLAUDE.md
+exclude coverage.xml
+exclude Makefile
+prune .github
+prune .stamps