Metadata-Version: 2.4
Name: pydaffodil
Version: 1.2.1
Summary: A cross-platform Python deployment framework for automated remote server deployments via SSH
Project-URL: Homepage, https://github.com/marcuwynu23/pydaffodil
Project-URL: Documentation, https://github.com/marcuwynu23/pydaffodil#readme
Project-URL: Repository, https://github.com/marcuwynu23/pydaffodil
Project-URL: Issues, https://github.com/marcuwynu23/pydaffodil/issues
Author-email: Mark Wayne Menorca <marcuwynu23@gmail.com>
License: MIT
License-File: LICENSE
Keywords: automation,ci-cd,cross-platform,deploy,deployment,devops,file-transfer,python-deployment,remote,remote-deployment,remote-execution,scp,server,ssh,ssh-deployment,vps
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: System Administrators
Classifier: Operating System :: MacOS
Classifier: Operating System :: Microsoft :: Windows
Classifier: Operating System :: OS Independent
Classifier: Operating System :: POSIX :: Linux
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Topic :: Internet :: File Transfer Protocol (FTP)
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Classifier: Topic :: System :: Archiving :: Packaging
Classifier: Topic :: System :: Installation/Setup
Classifier: Topic :: System :: Systems Administration
Requires-Python: >=3.9
Requires-Dist: colorama>=0.4.0
Requires-Dist: paramiko>=2.0.0
Requires-Dist: pyyaml>=6.0.0
Requires-Dist: tqdm>=4.60.0
Description-Content-Type: text/markdown

<div align="center">
  <h1>PyDaffodil</h1>
  <p><strong>Cross-Platform Deployment Automation Framework for Python</strong></p>
  <p>
    <img src="https://img.shields.io/pypi/v/pydaffodil?color=blue&label=PyPI" alt="PyPI version"/>
    <img src="https://img.shields.io/pypi/pyversions/pydaffodil?color=green" alt="Python versions"/>
    <img src="https://img.shields.io/pypi/dm/pydaffodil?color=orange" alt="PyPI downloads"/>
    <img src="https://img.shields.io/github/stars/marcuwynu23/pydaffodil.svg" alt="Stars"/>
    <img src="https://img.shields.io/github/license/marcuwynu23/pydaffodil.svg" alt="License"/>
  </p>
</div>

---

## Overview

**PyDaffodil** is a lightweight, declarative deployment automation framework for Python that simplifies remote server deployments over SSH. It provides a clear, step-oriented API for local commands, remote execution, and archive-based file transfer, with optional **watch-based** triggers and **multi-host** deployments via Ansible-style **`inventory.ini`** files.

### Key Features

- **Archive-Based File Transfer** — Packages local paths, transfers efficiently, and extracts on the remote host
- **Cross-Platform Support** — Runs on Windows, Linux, and macOS
- **SSH via Paramiko** — Key-based authentication (RSA, ECDSA, Ed25519, and others supported by Paramiko)
- **Step-by-Step Execution** — Chain deployment steps with readable progress output
- **Ignore Pattern Support** — `.scpignore` (or custom path) to exclude paths from transfers
- **Colored Terminal Output** — Clear logs via Colorama
- **Progress Feedback** — Transfer progress with tqdm
- **Watch-Based Workflows (`watch()`)** — Trigger deploys on file changes and/or Git activity (commits, merges, tags)
- **Multi-Host Deployments** — Same steps across multiple servers using `inventory.ini` groups

---

## Documentation and Examples

For hands-on usage, see the **`example/`** directory:

- `example/publish.py` — Basic scripted deployment
- `example/publish-multi.py` — Multi-host deployment with `inventory.ini`
- `example/publish-watch.py` — File and Git–triggered deploys with `watch()`
- `example/.daffodil.yml` — Reference schema for the YAML CLI

---

## Installation

```bash
pip install pydaffodil
```

Requires a supported Python 3.x (see PyPI classifiers) and network access to the remote host over SSH.

---

## Quick Start

```python
from pydaffodil import Daffodil

deployer = Daffodil(
    remote_user="deployer",
    remote_host="231.142.34.222",
    remote_path="/var/www/myapp",
    port=22,  # optional; default 22
)

steps = [
    {
        "step": "Transfer application files",
        "command": lambda: deployer.transfer_files("./dist", "/var/www/myapp"),
    },
    {
        "step": "Install dependencies",
        "command": lambda: deployer.ssh_command(
            "cd /var/www/myapp && npm install --production=false"
        ),
    },
    {
        "step": "Restart application",
        "command": lambda: deployer.ssh_command("pm2 restart myapp"),
    },
]

deployer.deploy(steps)
```

---

## API Reference

### Constructor

```python
Daffodil(
    remote_user=None,
    remote_host=None,
    remote_path=None,
    port=22,
    ssh_key_path=None,
    ssh_key_pass=None,
    scp_ignore=".scpignore",
    inventory=None,   # path to inventory.ini (multi-host mode)
    group=None,       # inventory group name (required if inventory is set)
)
```

In **single-host** mode, `remote_user` and `remote_host` are required. In **inventory** mode, hosts are loaded from `inventory.ini` and `group` must identify the section to use.

### Methods

#### `transfer_files(local_path, destination_path=None)`

Transfers a local file or directory to the remote server using an archive step, then extracts on the remote side. Honors `.scpignore` patterns.

#### `run_command(command)`

Runs a shell command on the **local** machine.

#### `ssh_command(command)`

Runs a command on the **remote** server over the active SSH session.

#### `make_directory(directory_name)`

Creates a directory on the remote server (under the configured remote context).

#### `deploy(steps)`

Runs deployment **steps** in order. Each step is a `dict` with:

- `step` — Human-readable label
- `command` — Callable (typically a `lambda`) returning the operation result

In **inventory** mode, the same steps are executed **sequentially per host**.

#### `watch(...)`

Returns a watch session with a `.deploy(steps)` method. Configure file paths, Git repo path, branches, tags, events, debounce, and polling interval.

```python
deployer.watch(
    paths=["./dist", "./src"],
    debounce=2000,          # ms between eligible deploys after a trigger
    repo_path=".",
    branches=["main", "staging"],
    tags=True,
    tag_pattern=r"^v\d+\.\d+\.\d+$",  # regex string; optional
    events=["commit", "merge", "tag"],
    interval=5000,          # poll interval in ms
).deploy(steps)
```

---

## Advanced Topics

### Archive-Based Transfer

PyDaffodil builds an archive of the selected local content, transfers it, and extracts it remotely. This reduces round-trips and works well for larger trees and slower links.

### Ignore Patterns (`.scpignore`)

Place a `.scpignore` in your project (or point `scp_ignore` at another file). Patterns exclude matching paths from transfer, similar in spirit to `.gitignore`-style workflows.

### SSH Keys

Provide `ssh_key_path` (and `ssh_key_pass` if the key is encrypted), or rely on Paramiko’s default key discovery where applicable.

---

## Best Practices

### SSH Access

Ensure key-based login works before automating:

```bash
ssh-keygen -t ed25519 -C "you@example.com"
ssh-copy-id deployer@your-server
ssh deployer@your-server
```

### Error Handling

Wrap deploy scripts in `try` / `except` and exit with a non-zero status in CI.

### Secrets

Prefer environment variables or a secrets manager for hosts, users, and keys—not hard-coded credentials in source control.

### Conditional Steps

Build the `steps` list dynamically (e.g. only run migrations in production) using ordinary Python control flow.

---

## Configuration Options

| Option          | Type    | Default         | Description |
| --------------- | ------- | --------------- | ----------- |
| `remote_user`   | `str`   | —               | SSH username (single-host mode) |
| `remote_host`   | `str`   | —               | Hostname or IP (single-host mode) |
| `remote_path`   | `str`   | auto / `.`      | Default remote base path |
| `port`          | `int`   | `22`            | SSH port |
| `ssh_key_path`  | `str`   | `None`          | Path to private key |
| `ssh_key_pass`  | `str`   | `None`          | Key passphrase, if needed |
| `scp_ignore`    | `str`   | `".scpignore"` | Ignore file path |
| `inventory`     | `str`   | `None`          | Path to `inventory.ini` (multi-host) |
| `group`         | `str`   | `None`          | Inventory group name (e.g. `webservers`) |

---

## Watch-Based CI/CD

Use `watch()` to run the same `deploy(steps)` pipeline when files change or Git state updates. See `example/` for patterns; combine `paths` with `repo_path` for file + Git triggers.

---

## Multi-Host Deployments with `inventory.ini`

Use an Ansible-style INI file to target a group of hosts with one script.

### Example `inventory.ini`

```ini
[webservers]
server1 host=231.142.34.222 user=deployer port=22
server2 host=231.142.34.223 user=deployer
server3 host=231.142.34.224 user=ubuntu port=2200
```

### Programmatic usage

```python
from pydaffodil import Daffodil

deployer = Daffodil(
    inventory="./inventory.ini",
    group="webservers",
    remote_path="/var/www/myapp",
)

deployer.deploy(steps)
```

See `example/publish-multi.py` and `example/inventory.ini` for a complete layout.

---

## Requirements

- **Python** 3.x (see [PyPI](https://pypi.org/project/pydaffodil/) for supported versions)
- **SSH** connectivity to the remote host
- **Dependencies** (installed with the package): `paramiko`, `tqdm`, `colorama`

---

## YAML CLI Deployment

PyDaffodil includes a CLI that reads `.daffodil.yml`:

```bash
pydaffodil --config example/.daffodil.yml
pydaffodil --config example/.daffodil.yml --watch
```

The config filename must be exactly **`.daffodil.yml`**.

**Other official CLIs (same YAML):** [JSDaffodil](https://www.npmjs.com/package/@marcuwynu23/jsdaffodil) uses `jsdaffodil --config`; [GoDaffodil](https://github.com/marcuwynu23/godaffodil) uses `godaffodil run --config` (no other subcommands).

### Host resolution (CLI)

Hosts are resolved in this order:

1. Inline **`hosts`** in the YAML file (if present and non-empty)
2. **`inventoryFile`** + **`inventoryGroup`** (Ansible-style `inventory.ini`)
3. Top-level **`remoteHost` / `remoteUser`** (or snake_case equivalents) for a single default host

Optional inventory reference:

```yaml
inventoryFile: inventory.ini
inventoryGroup: webservers
```

---

## Contributing

Contributions are welcome. Open an issue to discuss larger changes, then submit a pull request with a clear description and tests where appropriate.

The library code lives under `src/pydaffodil/`.

### Local setup with uv

From the repository root:

```bash
uv sync
```

That creates `.venv/`, installs the project in editable mode, and pulls dev dependencies (build tools, and so on). Use `uv run …` so commands use that environment without activating the venv manually.

### CLI in development

Run the CLI through uv so it uses the local package:

```bash
uv run pydaffodil
```

Other equivalent entry points:

```bash
uv run python -m pydaffodil
uv run python -m pydaffodil.cli
```

The CLI looks for a config file named **`.daffodil.yml`** in the current working directory. To try the sample config under `example/`:

```bash
uv run --directory example pydaffodil
```

Or:

```bash
cd example
uv run pydaffodil
```

(Add `--watch` for watch mode when your YAML defines it.)

### Tests

From the repository root:

```bash
uv run python -m unittest discover -s tests -v
```

---

## License

[MIT License](./LICENSE)

---

## Acknowledgments

- SSH: [Paramiko](https://www.paramiko.org/)
- Progress: [tqdm](https://github.com/tqdm/tqdm)
- Terminal colors: [Colorama](https://github.com/tartley/colorama)

Sister projects: [JSDaffodil](https://www.npmjs.com/package/@marcuwynu23/jsdaffodil) (Node.js), [GoDaffodil](https://github.com/marcuwynu23/godaffodil) (Go).

---

<div align="center">
  <p>Made with care by <a href="https://github.com/marcuwynu23">Mark Wayne B. Menorca</a></p>
</div>
