arkitekt-gateway 0.1.0__tar.gz

arkitekt_gateway-0.1.0/.github/workflows/coverage.yaml

@@ -0,0 +1,36 @@
+name: Run Coverage
+
+on:
+  pull_request:
+    branches: [main] # or any branches you want to target
+  push:
+    branches: [main]
+
+jobs:
+  run_tests:
+    name: Python (Pull Request Tests)
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv and set Python
+        uses: astral-sh/setup-uv@v6
+        with:
+          version: "latest"
+          python-version: "3.12"
+
+      - uses: pyvista/setup-headless-display-action@v3
+        with:
+          qt: true
+
+      - name: Install the project
+        run: uv sync --all-extras --dev
+
+      - name: Run tests
+        run: uv run pytest --cov --cov-branch --cov-report=xml
+
+      - name: Upload coverage reports to Codecov
+        uses: codecov/codecov-action@v5
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}

arkitekt_gateway-0.1.0/.github/workflows/release.yaml

@@ -0,0 +1,48 @@
+name: Release with uv and semantic-release
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  id-token: write
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Install uv and set Python
+        uses: astral-sh/setup-uv@v6
+        with:
+          version: "latest"
+          python-version: "3.12"
+
+      - uses: pyvista/setup-headless-display-action@v3
+        with:
+          qt: true
+
+      - name: Install dependencies
+        run: uv sync --all-extras --dev
+
+      - name: Run tests
+        run: uv run pytest tests
+
+      - name: Run semantic-release
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: uv run semantic-release version
+
+      - name: Publish to Releases
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: uv run semantic-release publish
+
+      - name: Publish to Pypi
+        run: uv publish

arkitekt_gateway-0.1.0/.github/workflows/tests.yaml

@@ -0,0 +1,32 @@
+name: CI
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+jobs:
+  test_suit:
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12"]
+        os: [windows-latest, ubuntu-latest]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv and set the python version
+        uses: astral-sh/setup-uv@v6
+        with:
+          version: "latest"
+          python-version: ${{ matrix.python-version }}
+
+      - uses: pyvista/setup-headless-display-action@v3
+        with:
+          qt: true
+
+      - name: Install the project
+        run: uv sync --all-extras --dev
+
+      - name: Run tests
+        run: uv run pytest

arkitekt_gateway-0.1.0/.gitignore

@@ -0,0 +1,152 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+**/__pycache__
+*.py[cod]
+*$py.class
+*.pyc
+*.DS_Store
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# 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.
+
+*.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
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__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/
+
+# static files generated from Django application using `collectstatic`
+media
+export
+static_collected
+data
+token.temp
+arkitekt_server_config.yaml
+# Arkitekt server config file
+# This file is automatically generated and should not be modified manually.
+# It contains sensitive information and should not be committed to version control.

arkitekt_gateway-0.1.0/.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "python-envs.pythonProjects": []
+}

arkitekt_gateway-0.1.0/CHANGELOG.md

@@ -0,0 +1,20 @@
+# CHANGELOG
+
+
+## v0.1.0 (2026-01-19)
+
+### Bug Fixes
+
+- Do
+  ([`209be5d`](https://github.com/arkitektio/arkitekt-gateway/commit/209be5dc60d9c074b324199b29db16fc91819b4c))
+
+- Fix tests
+  ([`d9d157f`](https://github.com/arkitektio/arkitekt-gateway/commit/d9d157fddc2f92aba2043e15983011056a9c5a83))
+
+- Fix tests
+  ([`53e3430`](https://github.com/arkitektio/arkitekt-gateway/commit/53e3430abff6b59c65a0f5b28ff25156cec7df94))
+
+### Features
+
+- Test
+  ([`9a5336b`](https://github.com/arkitektio/arkitekt-gateway/commit/9a5336bcc1ea64863ee53744fa938e0d2f42cb80))

arkitekt_gateway-0.1.0/PKG-INFO

@@ -0,0 +1,210 @@
+Metadata-Version: 2.4
+Name: arkitekt-gateway
+Version: 0.1.0
+Summary: Add your description here
+Author-email: Your Name <your.email@example.com>
+Keywords: arkitekt,gateway
+Classifier: Development Status :: 4 - Beta
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.11
+Requires-Dist: typer>=0.16.0
+Description-Content-Type: text/markdown
+
+# Arkitekt Server
+
+A command-line tool for deploying and managing an Arkitekt server deployments. Arkitekt Server provides a comprehensive platform for scientific computing and data management, with built-in support for authentication, task orchestration, data storage, and containerized application deployment.
+
+## Overview
+
+Arkitekt Server is a deployment configuration management tool that simplifies the setup and management of the Arkitekt ecosystem. It generates Docker Compose configurations and handles the complex orchestration of multiple services including databases, message queues, object storage, and various scientific computing services.
+
+## Quick Start: How to Start the Server
+
+### Prerequisites
+- Python 3.12+
+- Docker and Docker Compose
+- UVX (recommended) or pip
+
+### 1. Initialize Your Deployment
+```bash
+# Initialize in the current directory (interactive wizard)
+uvx arkitekt-server init --wizard
+
+# Initialize with a specific template (default, dev, minimal)
+uvx arkitekt-server init --template default
+
+# Initialize in a specific directory
+uvx arkitekt-server init --template dev ./my-server
+```
+
+
+
+### 2. Set Up Users and Organizations
+```bash
+# Add a user
+uvx arkitekt-server user add
+
+# Add an organization
+uvx arkitekt-server organization add
+```
+
+### 3. Build and Start
+```bash
+# Generate deployment files (auto-detects backend)
+uvx arkitekt-server build
+
+# Start the services (using docker compose directly for now)
+docker compose up -d
+```
+
+### 4. Access Your Server
+Wait for services to initialize, then access via the Arkitekt Orkestrator interface at the configured URL (usually http://localhost:8000).
+
+## Temporary Server (Ephemeral Mode)
+
+For quick testing, demos, or development without leaving any trace, you can use the ephemeral mode. This creates a temporary server instance in a temporary directory, starts it, and cleans everything up when you stop it.
+
+```bash
+# Start a temporary server on port 23489 (default)
+uvx arkitekt-server ephemeral
+
+# Start on a specific port
+uvx arkitekt-server ephemeral --port 8080
+```
+
+This is perfect for trying out Arkitekt or running integration tests.
+
+## Command Reference
+
+### Core Commands
+
+- **`init`**: Initializes a new Arkitekt server configuration.
+  - `--wizard`: Runs an interactive wizard to guide you through setup.
+  - `--template [default|dev|minimal]`: Uses a predefined template.
+  - `[path]`: Specifies the directory to initialize (default: current directory).
+
+- **`build`**: Generates the deployment files (e.g., `docker-compose.yaml`) based on your configuration.
+  - `--dry-run`: Shows what would be generated without writing files.
+
+- **`start`**: Starts the server services using the generated deployment files.
+  - Equivalent to running `docker compose up -d`.
+
+- **`update`**: Updates the server images and restarts services.
+  - Pulls the latest Docker images and runs `up -d`.
+
+- **`ephemeral`**: Starts a temporary, disposable server instance.
+  - `--port`: Sets the HTTP port.
+  - `--defaults`: Skips prompts and uses default settings.
+
+### Management Commands
+
+- **`service`**: Manage individual Arkitekt services (Rekuest, Mikro, etc.).
+  - `[service_name] --enable/--disable`: Enable or disable a service.
+  - `list`: List all available services and their status.
+
+- **`user`**: Manage users for the Arkitekt deployment.
+  - `add`: Create a new user (interactive).
+  - `list`: List all configured users.
+  - `delete`: Remove a user.
+
+- **`organization`**: Manage organizations.
+  - `add`: Create a new organization.
+  - `list`: List all configured organizations.
+
+- **`inspect`**: Inspect the current state and configuration.
+  - `config`: Displays the current configuration and enabled services.
+
+## Detailed Documentation
+
+For comprehensive documentation, see the `docs/` folder:
+
+- **[📚 Getting Started Guide](docs/starting.md)** - Step-by-step setup instructions
+- **[⚙️ Configuration Guide](docs/configuration.md)** - Detailed configuration options
+- **[🔧 Services Overview](docs/services.md)** - Complete service descriptions  
+- **[🏗️ Architecture Guide](docs/architecture.md)** - Deployment patterns and architecture
+
+## Oh my god, I forgot all of my passwords!
+
+If you forget your preconfiugred user passwords, you can reset them by running:
+
+```bash
+uvx arkitekt-server user list
+```
+
+This command will list all users and their roles, that you have configured previously.
+Of course you would never use this in production, but it is a useful command for development and testing purposes.
+
+
+### Non-UVX Usage
+
+If you prefer not to use UVX, you can run the tool directly with:
+
+```bash
+pip install arkitekt-server
+arkitekt-server init --template default
+```
+
+## Key Features
+
+- **One-Command Deployment**: Generate complete Docker Compose configurations with sensible defaults
+- **Service Deployment**: Deploy and manage multiple interconnected services
+- **Authentication & Authorization**: Built-in user management with JWT-based authentication
+- **Development Mode**: Hot-reload support for development with GitHub repository mounting (when available)
+
+## Core Services
+
+The Arkitekt ecosystem includes several specialized services:
+
+- **Lok**: Authentication and authorization service with JWT token management
+- **Rekuest**: Task orchestration and workflow management
+- **Mikro**: Image and microscopy data management
+- **Kabinet**: Container and application registry
+- **Fluss**: Workflow execution engine
+- **Kraph**: Knowledge graph and metadata management
+- **Elektro**: Electrophysiology data handling
+- **Alpaka**: AI/ML model management with Ollama integration
+
+## Configuration
+
+The tool generates and manages a `arkitekt_server_config.yaml` file that contains all deployment settings. This file includes:
+
+- Service configurations and Docker images
+- Database and Redis settings
+- Object storage (MinIO) configuration
+- Authentication keys and secrets
+- User and group management
+- Network and routing configuration
+
+This file can be customized to suit your deployment needs, allowing you to specify local or remote databases, shared or dedicated storage buckets, and development or production deployment modes. This config-file is the central point for managing your Arkitekt Server deployment. And it is automatically generated based on the services you enable and the options you choose during initialization.
+
+## Architecture
+
+Arkitekt Server uses a self-contained service architecture with:
+
+- **PostgreSQL**: Primary database for all services
+- **Redis**: Message queuing and caching
+- **MinIO**: S3-compatible object storage
+- **Caddy**: Reverse proxy and gateway
+- **Docker**: Container orchestration
+
+Each service can be configured independently with options for:
+- Local or remote databases
+- Shared or dedicated storage buckets
+- Development or production deployment modes
+- Custom authentication configurations
+
+## Development
+
+For development workflows, the tool supports:
+
+- GitHub repository mounting for live code reloading
+- Debug mode with detailed logging
+- Separate development configurations
+
+
+## License
+
+MIT License

arkitekt_gateway-0.1.0/README.md

@@ -0,0 +1,195 @@
+# Arkitekt Server
+
+A command-line tool for deploying and managing an Arkitekt server deployments. Arkitekt Server provides a comprehensive platform for scientific computing and data management, with built-in support for authentication, task orchestration, data storage, and containerized application deployment.
+
+## Overview
+
+Arkitekt Server is a deployment configuration management tool that simplifies the setup and management of the Arkitekt ecosystem. It generates Docker Compose configurations and handles the complex orchestration of multiple services including databases, message queues, object storage, and various scientific computing services.
+
+## Quick Start: How to Start the Server
+
+### Prerequisites
+- Python 3.12+
+- Docker and Docker Compose
+- UVX (recommended) or pip
+
+### 1. Initialize Your Deployment
+```bash
+# Initialize in the current directory (interactive wizard)
+uvx arkitekt-server init --wizard
+
+# Initialize with a specific template (default, dev, minimal)
+uvx arkitekt-server init --template default
+
+# Initialize in a specific directory
+uvx arkitekt-server init --template dev ./my-server
+```
+
+
+
+### 2. Set Up Users and Organizations
+```bash
+# Add a user
+uvx arkitekt-server user add
+
+# Add an organization
+uvx arkitekt-server organization add
+```
+
+### 3. Build and Start
+```bash
+# Generate deployment files (auto-detects backend)
+uvx arkitekt-server build
+
+# Start the services (using docker compose directly for now)
+docker compose up -d
+```
+
+### 4. Access Your Server
+Wait for services to initialize, then access via the Arkitekt Orkestrator interface at the configured URL (usually http://localhost:8000).
+
+## Temporary Server (Ephemeral Mode)
+
+For quick testing, demos, or development without leaving any trace, you can use the ephemeral mode. This creates a temporary server instance in a temporary directory, starts it, and cleans everything up when you stop it.
+
+```bash
+# Start a temporary server on port 23489 (default)
+uvx arkitekt-server ephemeral
+
+# Start on a specific port
+uvx arkitekt-server ephemeral --port 8080
+```
+
+This is perfect for trying out Arkitekt or running integration tests.
+
+## Command Reference
+
+### Core Commands
+
+- **`init`**: Initializes a new Arkitekt server configuration.
+  - `--wizard`: Runs an interactive wizard to guide you through setup.
+  - `--template [default|dev|minimal]`: Uses a predefined template.
+  - `[path]`: Specifies the directory to initialize (default: current directory).
+
+- **`build`**: Generates the deployment files (e.g., `docker-compose.yaml`) based on your configuration.
+  - `--dry-run`: Shows what would be generated without writing files.
+
+- **`start`**: Starts the server services using the generated deployment files.
+  - Equivalent to running `docker compose up -d`.
+
+- **`update`**: Updates the server images and restarts services.
+  - Pulls the latest Docker images and runs `up -d`.
+
+- **`ephemeral`**: Starts a temporary, disposable server instance.
+  - `--port`: Sets the HTTP port.
+  - `--defaults`: Skips prompts and uses default settings.
+
+### Management Commands
+
+- **`service`**: Manage individual Arkitekt services (Rekuest, Mikro, etc.).
+  - `[service_name] --enable/--disable`: Enable or disable a service.
+  - `list`: List all available services and their status.
+
+- **`user`**: Manage users for the Arkitekt deployment.
+  - `add`: Create a new user (interactive).
+  - `list`: List all configured users.
+  - `delete`: Remove a user.
+
+- **`organization`**: Manage organizations.
+  - `add`: Create a new organization.
+  - `list`: List all configured organizations.
+
+- **`inspect`**: Inspect the current state and configuration.
+  - `config`: Displays the current configuration and enabled services.
+
+## Detailed Documentation
+
+For comprehensive documentation, see the `docs/` folder:
+
+- **[📚 Getting Started Guide](docs/starting.md)** - Step-by-step setup instructions
+- **[⚙️ Configuration Guide](docs/configuration.md)** - Detailed configuration options
+- **[🔧 Services Overview](docs/services.md)** - Complete service descriptions  
+- **[🏗️ Architecture Guide](docs/architecture.md)** - Deployment patterns and architecture
+
+## Oh my god, I forgot all of my passwords!
+
+If you forget your preconfiugred user passwords, you can reset them by running:
+
+```bash
+uvx arkitekt-server user list
+```
+
+This command will list all users and their roles, that you have configured previously.
+Of course you would never use this in production, but it is a useful command for development and testing purposes.
+
+
+### Non-UVX Usage
+
+If you prefer not to use UVX, you can run the tool directly with:
+
+```bash
+pip install arkitekt-server
+arkitekt-server init --template default
+```
+
+## Key Features
+
+- **One-Command Deployment**: Generate complete Docker Compose configurations with sensible defaults
+- **Service Deployment**: Deploy and manage multiple interconnected services
+- **Authentication & Authorization**: Built-in user management with JWT-based authentication
+- **Development Mode**: Hot-reload support for development with GitHub repository mounting (when available)
+
+## Core Services
+
+The Arkitekt ecosystem includes several specialized services:
+
+- **Lok**: Authentication and authorization service with JWT token management
+- **Rekuest**: Task orchestration and workflow management
+- **Mikro**: Image and microscopy data management
+- **Kabinet**: Container and application registry
+- **Fluss**: Workflow execution engine
+- **Kraph**: Knowledge graph and metadata management
+- **Elektro**: Electrophysiology data handling
+- **Alpaka**: AI/ML model management with Ollama integration
+
+## Configuration
+
+The tool generates and manages a `arkitekt_server_config.yaml` file that contains all deployment settings. This file includes:
+
+- Service configurations and Docker images
+- Database and Redis settings
+- Object storage (MinIO) configuration
+- Authentication keys and secrets
+- User and group management
+- Network and routing configuration
+
+This file can be customized to suit your deployment needs, allowing you to specify local or remote databases, shared or dedicated storage buckets, and development or production deployment modes. This config-file is the central point for managing your Arkitekt Server deployment. And it is automatically generated based on the services you enable and the options you choose during initialization.
+
+## Architecture
+
+Arkitekt Server uses a self-contained service architecture with:
+
+- **PostgreSQL**: Primary database for all services
+- **Redis**: Message queuing and caching
+- **MinIO**: S3-compatible object storage
+- **Caddy**: Reverse proxy and gateway
+- **Docker**: Container orchestration
+
+Each service can be configured independently with options for:
+- Local or remote databases
+- Shared or dedicated storage buckets
+- Development or production deployment modes
+- Custom authentication configurations
+
+## Development
+
+For development workflows, the tool supports:
+
+- GitHub repository mounting for live code reloading
+- Debug mode with detailed logging
+- Separate development configurations
+
+
+## License
+
+MIT License

arkitekt_gateway-0.1.0/arkitekt_gateway/__init__.py

@@ -0,0 +1,4 @@
+from .main import main
+
+
+__all__ = ["main", "create_server"]