dev-code 0.1.0__tar.gz

dev_code-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,35 @@
+name: CI
+
+on:
+  push:
+    branches: ["**"]
+  pull_request:
+    branches: ["**"]
+
+jobs:
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Run tests
+        run: uvx tox -e py312
+
+      - name: Upload coverage to Codecov
+        if: matrix.os == 'ubuntu-latest'
+        uses: codecov/codecov-action@v5
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          files: coverage.xml
+          fail_ci_if_error: false

dev_code-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,26 @@
+name: Publish
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - uses: astral-sh/setup-uv@v5
+
+      - name: Build package
+        run: uv build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

dev_code-0.1.0/.gitignore

@@ -0,0 +1,176 @@
+# Created by https://www.toptal.com/developers/gitignore/api/python
+# Edit at https://www.toptal.com/developers/gitignore?templates=python
+
+### Python ###
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+### Python Patch ###
+# Poetry local configuration file - https://python-poetry.org/docs/configuration/#local-configuration
+poetry.toml
+
+# ruff
+.ruff_cache/
+
+# LSP config files
+pyrightconfig.json
+
+# End of https://www.toptal.com/developers/gitignore/api/python

dev_code-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Nasser Alansari
+
+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.

dev_code-0.1.0/PKG-INFO

@@ -0,0 +1,5 @@
+Metadata-Version: 2.4
+Name: dev-code
+Version: 0.1.0
+License-File: LICENSE
+Requires-Python: >=3.10

dev_code-0.1.0/README.md

@@ -0,0 +1,151 @@
+# dev-code
+
+```text
+     _                                _
+    | |                              | |
+  __| | _____   ________ ___ ___   __| | ___
+ / _` |/ _ \ \ / /______/ __/ _ \ / _` |/ _ \
+| (_| |  __/\ V /      | (_| (_) | (_| |  __/
+ \__,_|\___| \_/        \___\___/ \__,_|\___|
+  project · editor · container — simplified
+```
+
+[![Coverage](https://codecov.io/gh/dacrystal/dev-code/branch/main/graph/badge.svg)](https://codecov.io/gh/dacrystal/dev-code)
+
+[![PyPI version](https://img.shields.io/pypi/v/dev-code)](https://pypi.org/project/dev-code/)
+[![Python 3.10+](https://img.shields.io/pypi/pyversions/dev-code)](https://pypi.org/project/dev-code/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
+
+**One command. Any project. The right devcontainer.**
+
+`dev-code` is a CLI that opens any project in VS Code inside a devcontainer — instantly, using reusable templates you define once. No more hunting config files. No more copy-pasting `devcontainer.json`.
+
+---
+
+## Install
+
+```bash
+pip install dev-code
+```
+
+Or run without installing via **uvx**:
+
+```bash
+uvx dev-code
+```
+
+**Tip:** Add an alias for the fastest workflow:
+
+```bash
+alias dev-code="uvx dev-code"
+```
+
+> Requires: VS Code with the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) + Docker
+
+---
+
+## Quick-start
+
+```bash
+# 1. Seed your first template
+dev-code init
+
+# 2. Open any project in a devcontainer
+dev-code open dev-code ~/projects/my-app
+
+# That's it. VS Code opens, container spins up.
+```
+
+---
+
+## Features
+
+- **One-command open** — `dev-code open <template> <path>` launches VS Code in a devcontainer instantly
+- **Reusable templates** — define your devcontainer once, reuse it across every project
+- **Built-in template** — ships with the `dev-code` template out of the box
+- **Custom templates** — create and manage your own with `dev-code new`
+- **File sync on launch** — copy credentials, configs, and secrets into the container via a `dev-code` customization block in `devcontainer.json`
+- **WSL support** — works natively on Windows Subsystem for Linux
+- **Container dashboard** — see all running devcontainers with `dev-code ps`
+- **Works with existing config** — no new format, just standard `devcontainer.json`
+
+---
+
+## Commands
+
+| Command | Description |
+|---|---|
+| `dev-code init` | Seed the built-in `dev-code` template into your template directory |
+| `dev-code open <template> <path>` | Open a project in VS Code using a devcontainer template |
+| `dev-code new <name> [base]` | Create a new template (optionally based on an existing one) |
+| `dev-code edit [template]` | Open a template for editing in VS Code |
+| `dev-code list [--long]` | List available templates |
+| `dev-code ps` | Show running devcontainers |
+
+### Options
+
+| Flag | Command | Description |
+|---|---|---|
+| `--dry-run` | `open` | Print the devcontainer URI and copy plan without executing |
+| `--container-folder` | `open` | Override the in-container workspace path |
+| `--timeout` | `open` | Seconds to wait for container to start (default: 300) |
+| `--edit` | `new` | Open the new template for editing immediately after creation |
+| `--long` | `list` | Show full paths alongside template names |
+| `-v, --verbose` | all | Enable debug logging |
+
+---
+
+## Templates
+
+Templates are directories containing a `.devcontainer/devcontainer.json` file. They live in `~/.local/share/dev-code/templates/` by default (XDG-compliant), or wherever `$DEVCODE_TEMPLATE_DIR` points.
+
+### Get started
+
+```bash
+dev-code init                  # copies the built-in dev-code template
+dev-code new my-python         # creates a new template from the default base
+dev-code new my-node dev-code  # creates a new template based on dev-code
+dev-code edit my-python        # open the template in VS Code to customise it
+```
+
+### File sync — copy files into the container on launch
+
+Add a `customizations.dev-code.cp` section to your `devcontainer.json` to copy files from your host into the running container:
+
+```json
+{
+  "customizations": {
+    "dev-code": {
+      "cp": [
+        {
+          "source": "${localEnv:HOME}/.claude/credentials.json",
+          "target": "/home/vscode/.claude/credentials.json"
+        }
+      ]
+    }
+  }
+}
+```
+
+Supports `owner`, `group`, `permissions`, and `Override` fields per entry. Use `source/.` to copy the contents of a directory.
+
+---
+
+## Contributing
+
+Contributions are welcome! To get started:
+
+```bash
+git clone https://github.com/dacrystal/dev-code
+dev-code open dev-code ./dev-code
+```
+
+The repo includes a `dev-code` devcontainer — open it with itself.
+
+Please open an issue before submitting large changes.
+
+---
+
+## License
+
+MIT

dev_code-0.1.0/pyproject.toml

@@ -0,0 +1,29 @@
+[build-system]
+requires = ["hatchling", "hatch-vcs"]
+build-backend = "hatchling.build"
+
+[project]
+name = "dev-code"
+dynamic = ["version"]
+requires-python = ">=3.10"
+dependencies = []
+
+[project.scripts]
+dev-code = "dev_code:main"
+
+[tool.hatch.version]
+source = "vcs"
+
+[tool.hatch.build.targets.wheel]
+force-include = {"src/dev_code.py" = "dev_code.py", "src/templates" = "dev_code_templates"}
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+
+[dependency-groups]
+dev = [
+    "pytest>=7.0.1",
+    "pyfiglet>=1.0.4",
+    "pytest-cov>=4.0",
+    "tox>=4.0",
+]