pydorky 2.1.8

package/.devcontainer/devcontainer.json

@@ -0,0 +1,17 @@
+{
+  "name": "Pydorky Dev Container",
+  "image": "mcr.microsoft.com/vscode/devcontainers/javascript-node:16",
+  "updateRemoteUserUID": false,
+  "customizations": {
+    "vscode": {
+        "extensions": [
+        "esbenp.prettier-vscode",
+        "dbaeumer.vscode-eslint",
+        "ms-python.python"
+      ]
+    }
+  },
+  "postCreateCommand": "npm install",
+  "forwardPorts": [3000, 9229],
+  "remoteUser": "node"
+}

package/.github/FUNDING.yml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: Pratham-Jain-3903
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: # Replace with a single Buy Me a Coffee username
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

package/.github/workflows/e2e-integration.yml

@@ -0,0 +1,57 @@
+name: E2E integration (Node CLI + Python client)
+on:
+  pull_request:
+  push:
+    branches:
+      - '**'
+
+jobs:
+  e2e:
+    name: Node16 + Python integration
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js 16
+        uses: actions/setup-node@v4
+        with:
+          node-version: '16'
+
+      - name: Install root dependencies
+        run: npm ci
+
+      - name: Install server dependencies
+        run: |
+          cd server
+          npm ci
+
+      - name: Start server stub
+        run: |
+          cd server
+          nohup npm start > server.log 2>&1 &
+          # wait for server to be available
+          for i in {1..20}; do
+            if curl -sSf http://localhost:3000/ >/dev/null; then break; fi
+            sleep 1
+          done
+
+      - name: Node CLI smoke test
+        run: |
+          node --version
+          node bin/index.js --help || true
+
+      - name: Setup Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: '3.10'
+
+      - name: Install Python test deps and client
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest
+          pip install -e python-client
+
+      - name: Run Python client integration tests
+        run: |
+          pytest -q python-client/tests/test_integration.py

package/.github/workflows/publish.yml

@@ -0,0 +1,24 @@
+name: "🚀 Publish on npm"
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+    release:
+        name: 🚀 release
+        runs-on: ubuntu-latest
+        steps:
+            - name: Checkout
+              uses: actions/checkout@v4
+            - name: Setup node
+              uses: actions/setup-node@v3
+              with:
+                node-version: "16.x"
+                registry-url: 'https://registry.npmjs.org'
+            - run: npm install
+            - name: 🚀 publish
+              run: npm publish --access public
+              env:
+                  NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}

package/.nvmrc

@@ -0,0 +1 @@
+16

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022 Trishant Pahwa
+
+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.

package/README.md

@@ -0,0 +1,156 @@
+<div align="center">
+
+<!-- Logo Placeholder - Replace with actual logo -->
+<img
+  src="https://raw.githubusercontent.com/Pratham-Jain-3903/pydorky/main/rectdorky.png"
+  alt="Pydorky Logo"
+  width="500"
+  style="object-fit: cover; object-position: center;"
+/>
+
+
+# Pydorky
+
+**Practical artifact storage for teams**
+
+[![Build Status](https://github.com/Pratham-Jain-3903/pydorky/actions/workflows/e2e-integration.yml/badge.svg)](https://github.com/Pratham-Jain-3903/pydorky/actions/workflows/e2e-integration.yml)
+[![npm version](https://img.shields.io/npm/v/dorky.svg)](https://www.npmjs.com/package/dorky)
+[![License: ISC](https://img.shields.io/badge/License-ISC-blue.svg)](https://opensource.org/licenses/ISC)
+[![Python 3.8+](https://img.shields.io/badge/python-3.8+-blue.svg)](https://www.python.org/downloads/)
+[![Node.js 16+](https://img.shields.io/badge/node.js-16+-green.svg)](https://nodejs.org/)
+
+[Features](#vision) • [Quick Start](#quick-start) • [Documentation](docs/) • [CLI Usage](#node-npm-users--cli-and-legacy-usage)
+
+</div>
+
+---
+
+## Technology Stack
+
+<div align="center">
+
+### Core Technologies
+![Python](https://img.shields.io/badge/Python-3776AB?style=for-the-badge&logo=python&logoColor=white)
+![JavaScript](https://img.shields.io/badge/JavaScript-F7DF1E?style=for-the-badge&logo=javascript&logoColor=black)
+![Express](https://img.shields.io/badge/Express-000000?style=for-the-badge&logo=express&logoColor=white)
+
+### Documentation Stack Migration Pending
+![Node.js](https://img.shields.io/badge/Node.js-339933?style=for-the-badge&logo=nodedotjs&logoColor=white)
+![React](https://img.shields.io/badge/React-20232A?style=for-the-badge&logo=react&logoColor=61DAFB)
+
+### Cloud Storage Platforms
+![AWS](https://img.shields.io/badge/AWS_S3-232F3E?style=for-the-badge&logo=amazonaws&logoColor=white)
+![Google Cloud](https://img.shields.io/badge/Google_Cloud-4285F4?style=for-the-badge&logo=googlecloud&logoColor=white)
+![Azure](https://img.shields.io/badge/Azure-0078D4?style=for-the-badge&logo=microsoftazure&logoColor=white)
+
+</div>
+
+---
+
+## Introduction
+
+This repository is Pydorky, a Python-first client and ecosystem built around a small language-agnostic artifact service. Pydorky was inspired by the original `dorky` tool — originally authored by Trishant Pahwa — and extends the idea with data-focused features and a Python client optimized for data teams. The original project provided the foundation; this fork focuses the design on reliability, data ergonomics, and reproducible sharing.
+
+## Vision
+
+Teams should never lose important artifacts in chat threads, ad-hoc paste tools, or personal drives. Pydorky offers a reproducible, privacy-aware, and developer-friendly way to store project artifacts (secrets, environment files, small datasets, and binaries) in user-controlled storage (S3, GCS, etc.).
+
+## Why we built this
+
+I grew tired of important artifacts being scattered across chat apps (Teams, Slack), quick paste services (sharetext.io), and personal drives. That pattern causes lost context, duplicate uploads, and potential leaks. Pydorky provides a minimal, auditable, and automated alternative that:
+
+- keeps artifacts out of VCS while enabling reproducible sharing
+- integrates with existing cloud storage and IAM controls
+- provides lightweight metadata, idempotency, and streaming-friendly APIs
+- offers a Python client for data teams (Parquet/pyarrow integration) and thin clients for other languages
+
+## Approach
+
+Keep the service small and language-agnostic. Implement a canonical HTTP service for storage semantics (streaming upload/download, idempotency keys, metadata, hierarchical sync). Language clients — Python and Node — remain thin translators that implement ergonomic workflows (`commit`, `stage`, `push`). Heavy data-format work (Parquet conversions, large-table transforms) is handled by optional Python tools or sidecar converters.
+
+## Quick start
+
+### Install Python Client
+
+```bash
+pip install -e python-client
+```
+
+### Run Local Service
+
+```bash
+cd server
+npm install
+npm start
+```
+
+### Upload with Python Client
+
+```python
+from dorky_client import DorkyClient
+client = DorkyClient('http://localhost:3000')
+client.upload('path/to/file', metadata={'note':'example'})
+```
+
+## Where to look next
+
+Implementation notes and design rationale: see `docs/` (architecture, migration plan, Python client notes).
+
+## Acknowledgements
+
+This project builds on and refines the ideas in the original `dorky` project. See `docs/` for more on differences and the migration path.
+
+## Node (npm) users — CLI and legacy usage
+
+We continue to support the original Node/npm CLI workflows so JavaScript and Ops users can keep using the familiar commands.
+
+### Install CLI Globally
+
+```bash
+npm install -g dorky
+```
+
+### Quick CLI Commands
+
+- Initialize for AWS S3: `dorky --init aws`
+- Initialize for Google Drive: `dorky --init google-drive`
+- List files: `dorky --list` (respects `.dorkyignore`)
+- Add to stage: `dorky --add <file>`
+- Remove from stage: `dorky --rm <file>`
+- Push staged files: `dorky --push`
+- Pull files from remote: `dorky --pull`
+
+## AWS S3 Notes
+
+1. Create an S3 bucket and configure `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` in your environment.
+2. Use `dorky --init aws` to set up local metadata and `.dorkyignore`.
+3. Use `dorky --add`, `dorky --push`, `dorky --pull` as your normal workflow.
+
+## Google Drive Notes
+
+1. Use `dorky --init google-drive` and follow the OAuth setup instructions.
+2. Use the same `--add`, `--push`, `--pull` flow as above.
+
+## Developer & Compatibility Notes
+
+- The repo contains both the Node CLI and a Python client. The canonical storage semantics are provided by a small HTTP service; clients are thin translators.
+- Current Node compatibility: project targets Node 16 (`.nvmrc` + `engines.node`), with a planned migration to Node 20. See `docs/doc#3 the-correct-node-version`.
+- Python users: see `python-client/` for the PyPI-ready client scaffold and `docs/doc#2.5 python-port` for design notes.
+
+---
+
+<div align="center">
+
+## License
+
+This project is licensed under the ISC License - see the [LICENSE](LICENSE) file for details.
+
+## Contributing
+
+Contributions are welcome! Please feel free to submit a Pull Request.
+
+---
+
+**Made with care by the Pydorky contributors**
+
+</div>

package/bin/index.js

@@ -0,0 +1,19 @@
+#!/usr/bin/env node
+
+// Entry point that preserves legacy CLI behavior while we layer in a new
+// command-based CLI. For now, everything routes to the legacy implementation
+// to maintain backward compatibility.
+
+const { run: runLegacy } = require('./legacy');
+
+// Detect legacy-style invocations (flags like --init/--push/etc.)
+const rawArgs = process.argv.slice(2);
+const isLegacyInvocation = rawArgs.length === 0 || rawArgs.some(arg => arg.startsWith('--'));
+
+if (isLegacyInvocation) {
+  runLegacy(rawArgs);
+} else {
+  // Placeholder for future command-based CLI; keep legacy behavior for now.
+  runLegacy(rawArgs);
+}
+