@rakay-technology/kraft 0.7.4

package/README.md

@@ -0,0 +1,263 @@
+<h1 align="center">Kraft</h1>
+
+<p align="center">
+  Open-source, self-hostable deployment platform with built-in CI/CD.<br>
+  Point it at a repo — it builds, ships, routes, and TLS-terminates your app. Drive it from a desktop app, web dashboard, or CLI.
+</p>
+
+<p align="center">
+  <a href="https://trendshift.io/repositories/38817?utm_source=repository-badge&utm_medium=badge&utm_campaign=badge-repository-38817">
+    <img src="https://trendshift.io/api/badge/repositories/38817" alt="Trendshift" width="250" height="55" />
+  </a>
+</p>
+
+<p align="center">
+  <a href="https://www.npmjs.com/package/kraft"><img src="https://img.shields.io/npm/v/kraft?color=0b7285&label=npm" alt="npm version" /></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-blue" alt="License" /></a>
+  <a href="https://kraft.io"><img src="https://img.shields.io/badge/website-kraft.io-0b7285" alt="Website" /></a>
+</p>
+
+<p align="center">
+  <a href="#quick-start">Quick Start</a> ·
+  <a href="#how-it-works">How It Works</a> ·
+  <a href="#interfaces">Interfaces</a> ·
+  <a href="https://kraft.io/docs">Docs</a> ·
+  <a href="CONTRIBUTING.md">Contributing</a>
+</p>
+
+<p align="center">
+  <a href="README.md"><img src="https://img.shields.io/badge/lang-English-0b7285" alt="English" /></a>
+  <a href="docs/i18n/README.ar.md"><img src="https://img.shields.io/badge/lang-العربية-555" alt="العربية" /></a>
+  <a href="docs/i18n/README.zh.md"><img src="https://img.shields.io/badge/lang-简体中文-555" alt="简体中文" /></a>
+  <a href="docs/i18n/README.es.md"><img src="https://img.shields.io/badge/lang-Español-555" alt="Español" /></a>
+  <a href="docs/i18n/README.fr.md"><img src="https://img.shields.io/badge/lang-Français-555" alt="Français" /></a>
+  <a href="docs/i18n/README.ja.md"><img src="https://img.shields.io/badge/lang-日本語-555" alt="日本語" /></a>
+  <a href="docs/i18n/README.pt.md"><img src="https://img.shields.io/badge/lang-Português-555" alt="Português" /></a>
+  <a href="docs/i18n/README.de.md"><img src="https://img.shields.io/badge/lang-Deutsch-555" alt="Deutsch" /></a>
+  <a href="docs/i18n/README.tr.md"><img src="https://img.shields.io/badge/lang-Türkçe-555" alt="Türkçe" /></a>
+  <a href="docs/i18n/README.ko.md"><img src="https://img.shields.io/badge/lang-한국어-555" alt="한국어" /></a>
+</p>
+
+<p align="center">
+  <img src="docs/screenshots/screen.png" alt="Kraft dashboard" width="800" />
+</p>
+
+---
+
+## Quick Start
+
+There's one decision to make first: **how you run Kraft itself** (the control plane). Everything else is the same afterwards.
+
+| If you're…                                                             | Run Kraft as                        | Where your apps run                                                       |
+| ---------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------------------------------------- |
+| **Solo, one machine, no ops**                                          | **Desktop app**                     | A server you connect over SSH, or Kraft Cloud                             |
+| **A team — or you want push-to-deploy / to host apps on your own box** | **Self-hosted server** (`kraft up`) | On that box (Compose mode) — or out to another server / Cloud (bare mode) |
+| **Not interested in running anything**                                 | **Kraft Cloud**                     | Managed sandboxes, zero setup                                             |
+
+> [!TIP]
+> **Solo? Use the desktop app.** It runs Kraft's control plane on your own machine _only while the app is open_ — nothing is left running on an always-on server, nothing is exposed publicly. You only need an always-on server install once you want **push-to-deploy (CI/CD)**, **team access**, or to **host apps on that box** — the things that need a public, always-on endpoint.
+
+### Solo — desktop app
+
+The control plane runs locally and drives your servers over SSH. No login, no terminal, no public surface — download, open, done:
+
+| Platform                  | Download                                                                                                      |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| **macOS** (Apple Silicon) | [Kraft-arm64.dmg](https://github.com/rakay-technology/kraft/releases/latest/download/Kraft-arm64.dmg)         |
+| **macOS** (Intel)         | [Kraft-x64.dmg](https://github.com/rakay-technology/kraft/releases/latest/download/Kraft-x64.dmg)             |
+| **Windows**               | [Kraft-win32-x64.zip](https://github.com/rakay-technology/kraft/releases/latest/download/Kraft-win32-x64.zip) |
+| **Linux**                 | [Kraft.AppImage](https://github.com/rakay-technology/kraft/releases/latest/download/Kraft.AppImage)           |
+
+Linux: `chmod +x Kraft.AppImage && ./Kraft.AppImage`. Already have the CLI? `kraft install` fetches and launches it. Links always point at the newest release.
+
+From the desktop app you connect a server (SSH) or Kraft Cloud and deploy to it — the app itself doesn't host public apps on your laptop.
+
+### Team / always-on — self-hosted server
+
+Install the CLI (it bundles the API + dashboard), then run **`kraft`** — an interactive wizard creates the first admin, wires your domain, and installs Kraft as a boot service. Run it again anytime to manage the instance.
+
+```bash
+curl -fsSL https://get.kraft.io | sh          # install  (or: npm i -g @rakay-technology/kraft — needs Node 22+)
+kraft                                          # guided setup, then control panel
+```
+
+The install script brings its own Node when your system one is older than 22; a package-manager
+install runs on the Node you already have.
+
+For CI / headless boxes, skip the wizard and drive `kraft up` directly:
+
+```bash
+kraft up                                       # install + start as a background service (boots + auto-restarts)
+kraft up --public-url https://kraft.example.com   # + serve the dashboard on your domain (edge + TLS handled)
+```
+
+**`kraft up` picks how it runs for you:**
+
+- **On Linux with Docker → Compose mode** (the default). Brings up the full stack — Postgres, Redis, API, dashboard, and a containerized **OpenResty edge on :80/:443** — from published images. This is the flavor that **hosts your deployed apps on the same box**, with automatic domains + Let's Encrypt TLS. Force it with `--compose`.
+- **Everywhere else → bare mode** (macOS, Windows, or Linux without Docker). A single lightweight process with an embedded database — an always-on control plane that **deploys apps out to a server (SSH) or Cloud**, like the desktop app but always on and login-required. Force it with `--bare`.
+
+A self-hosted instance **always requires login** (the admin you create in setup). `kraft open` opens the dashboard · `kraft stop` stops it · `kraft update` upgrades · `kraft up --foreground` runs attached.
+
+> **Preview an unreleased build (dev).** To run the CLI built straight from source — a branch, tag, or `main` ahead of the next release — install the from-source build:
+>
+> ```bash
+> curl -fsSL https://get.kraft.io/dev | sh                  # main (default)
+> curl -fsSL https://get.kraft.io/dev | KRAFT_REF=dev sh  # a branch/tag (var goes on sh, not curl)
+> kraft-dev                                     # same CLI, built from source
+> kraft-dev update                              # pull latest source + rebuild (no release needed)
+> ```
+>
+> It installs as a **separate `kraft-dev`** command with its own isolated home (`~/.kraft-dev`) and boot service, so your production `kraft` and its data are never touched. Needs Bun + git; it's an unverified dev build (the dashboard compile wants real RAM/CPU) — not a production path.
+
+**Deploy a project:**
+
+```bash
+cd your-project
+kraft init            # link this directory to a project
+kraft deploy
+```
+
+Full server guide + complete CLI reference: **[kraft.io/docs](https://kraft.io/docs)**.
+
+<details>
+<summary>Shell completion (bash/zsh/fish)</summary>
+
+Two ways to enable Tab-completion for `kraft`:
+
+|                               | Setup                                                         | Trade-off                                                                                       |
+| ----------------------------- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| **Static file** (recommended) | `kraft completion <shell> > <path>`                           | Instant shell startup. Regenerate after upgrading to pick up newly added commands.              |
+| **Live-sourced**              | add `source <(kraft completion <shell>)` to your shell config | Always reflects the currently installed version. Adds a small delay to every new shell session. |
+
+**Static file:**
+
+```bash
+kraft completion bash > /etc/bash_completion.d/kraft
+kraft completion zsh  > ~/.zsh/completions/_kraft
+kraft completion fish > ~/.config/fish/completions/kraft.fish
+```
+
+Open a new terminal — done.
+
+**Live-sourced** (zsh example):
+
+```bash
+echo 'source <(kraft completion zsh)' >> ~/.zshrc
+```
+
+</details>
+
+<details>
+<summary>Self-host with raw Docker Compose (no CLI)</summary>
+
+The self-hosted stack lives in **`docker/docker-compose.yml`** and **pulls** published images from GitHub Container Registry (`ghcr.io/rakay-technology/*`) — no build tooling, no monorepo compile. Run it from the repo root:
+
+```bash
+git clone https://github.com/rakay-technology/kraft.git && cd kraft
+cp .env.example .env          # then edit
+docker compose --env-file .env -f docker/docker-compose.yml up -d
+```
+
+The stack is **postgres + redis + api + dashboard + edge**. The `edge` is OpenResty on **:80/:443** as a container (`network_mode: host`) — routing + Let's Encrypt, no bare host install. **Linux only** (host networking); on mac/win use `kraft up` (bare). The `api` container mounts the host Docker socket so the control plane can build + run your apps as host containers — it's host-privileged through the socket, so run it only on a trusted host.
+
+**Upgrade:** pin `KRAFT_VERSION` in `.env` for reproducible pulls, then `docker compose --env-file .env -f docker/docker-compose.yml pull && … up -d`. `kraft update` only reconciles a stack the CLI installed, and `kraft up` would _adopt_ this one — don't reach for either here. **Build from source instead:** add `-f docker/docker-compose.build.yml … up -d --build`.
+
+**Host operations** (`:80`/`:443` takeover, the mail engine, host terminal/port scans) need the container→host SSH channel, which `kraft up` provisions and this path does not — the five manual steps are in `.env.example` under _Host operations from the container_, and the failure it produces is [Troubleshooting → Host control channel](https://kraft.io/docs/troubleshooting/host-channel). Everything else, including deploys, works without it.
+
+> The **root** `docker-compose.yml` is a different file: it's the SaaS / from-source **control plane** (builds from source, ships the marketing site, no edge/socket). It does **not** self-host your apps — use `docker/docker-compose.yml` above or `kraft up`.
+
+</details>
+
+---
+
+## How It Works
+
+Point Kraft at a source — a **GitHub repo**, a **local folder**, or a **prebuilt artifact** — and it runs one pipeline end to end:
+
+1. **Detect.** It reads your `package.json`, framework config, lockfiles, and any `docker-compose.yml` / `kraft.json` to work out the stack, package manager, build/start commands, and port. Zero config files required; an `kraft.json` overrides the guesses if you want control.
+2. **Build.** On the target server or locally on the orchestrator, into a Docker image or a bare release. The resolved config is frozen into a snapshot, so redeploys and rollbacks re-run _exactly_ what shipped.
+3. **Run.** As a container (published on loopback only — never a public port) or a supervised host process.
+4. **Route + secure.** The OpenResty edge writes a reverse-proxy vhost to your domain and issues a Let's Encrypt certificate (HTTP-01). Because routing and TLS happen _after_ the app is up, a DNS or cert hiccup surfaces as "action required" — it never fails the deploy or takes your app down.
+5. **Push-to-deploy.** A GitHub webhook re-runs the pipeline on every push to the tracked branch — rebuilding only the services a monorepo push actually touched.
+
+Databases, domains, SSL, CDN, mail, and backups are managed from the same place. (Push-to-deploy and public domains need an always-on server or Cloud — a desktop/loopback instance has no public endpoint to receive webhooks.)
+
+---
+
+## Interfaces
+
+Three ways to drive the same backend:
+
+- **Desktop app** — full GUI, real-time logs, one-click everything. Best for solo.
+- **Web dashboard** — the same UI in the browser, built for teams.
+- **CLI** — scriptable and CI-friendly; also how you install and manage a self-hosted instance.
+
+An **MCP** endpoint (for AI agents) and a **REST API** round it out for automation. Only routes that opt in are exposed as MCP tools, every call re-checks your permissions, and credential/token routes can never become tools. Full reference at [kraft.io/docs](https://kraft.io/docs).
+
+> [!NOTE]
+> The docs are actively being filled out. If something's missing or unclear, [contributions](CONTRIBUTING.md) are hugely welcome.
+
+---
+
+## Features
+
+|                          |                                                                                                                                                         |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Built-in CI/CD**       | Push-to-deploy, preview environments, staging/prod flows, rollbacks                                                                                     |
+| **Any stack**            | Node, Python, Go, Rust, PHP, Ruby, Java, .NET, Docker, monorepos                                                                                        |
+| **Full backend**         | Postgres, MySQL, MongoDB, Redis, workers, WebSockets, storage                                                                                           |
+| **Domains & SSL**        | Automatic Let's Encrypt, wildcards, unlimited domains, auto-renewal                                                                                     |
+| **CDN**                  | Edge caching, HTTP/3, Brotli compression, instant purge                                                                                                 |
+| **Mail server**          | Built-in SMTP with DKIM/SPF/DMARC — no Mailgun or SES needed                                                                                            |
+| **Backups**              | Scheduled, databases + volumes, one-click restore, export anytime                                                                                       |
+| **Real-time monitoring** | Live build logs, container metrics, visitor geography and per-code response mix — [~1.4 µs per request, zero DB writes per request](docs/monitoring.md) |
+| **Scaling**              | Auto-scaling on cloud, multi-node ready on self-hosted                                                                                                  |
+| **Portability**          | Standard Docker containers — move between providers freely                                                                                              |
+| **Docker Compose**       | Deploy existing compose files as-is                                                                                                                     |
+
+---
+
+## Deploy Anywhere
+
+- **Kraft Cloud** — managed, auto-scaling, zero setup
+- **Any VPS** — Hetzner, DigitalOcean, Linode, OVH, and the rest
+- **Dedicated servers** — bare metal, colo, homelab
+- **Multi-server** — spread workloads across machines
+
+Same interface regardless of where you deploy.
+
+---
+
+## Status
+
+Production-ready core, actively developed. Self-hosting is **free** (no billing).
+
+**Coming next:** multi-node clusters, load-balancing UI, private networking, advanced monitoring, and visual CI/CD pipelines.
+
+---
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+---
+
+## Security
+
+Found a vulnerability? We welcome your report — please disclose it **privately**,
+never in a public issue, PR, or discussion.
+
+- **Report it here (preferred):** [Report a vulnerability](https://github.com/rakay-technology/kraft/security/advisories/new) — a private GitHub advisory, visible only to you and the maintainers.
+- Scope, what to include, and our response/disclosure process: [SECURITY.md](SECURITY.md).
+
+Good-faith security research is **authorized** under our
+[safe-harbor policy](SECURITY.md#safe-harbor), and we're happy to credit valid
+first reports.
+
+## License
+
+Kraft is **open-source** software, licensed under the [Apache License 2.0](LICENSE).
+
+You may use, run, modify, self-host, and distribute it — including in commercial
+and closed-source products — under the terms of the Apache 2.0 license. See
+[LICENSE](LICENSE) for the full text.

package/dist/bare-HL2GUYE2.js

@@ -0,0 +1,27 @@
+#!/usr/bin/env sh
+":" //# ; exec "$(command -v node || command -v bun)" "$0" "$@"
+import { createRequire as __ospCreateRequire } from "node:module";
+const require = __ospCreateRequire(import.meta.url);
+import {
+  BareRuntime,
+  STATIC_RELEASE_BASE
+} from "./chunk-DM3PKWDC.js";
+import "./chunk-AJ4QZLZ2.js";
+import "./chunk-MOLPYPVH.js";
+import "./chunk-ZVFS4LUA.js";
+import "./chunk-XGCG4MD5.js";
+import "./chunk-HMJUFZK7.js";
+import "./chunk-XVKUFMIB.js";
+import "./chunk-S3QBGGVP.js";
+import "./chunk-WYNM7L22.js";
+import "./chunk-N4OALTFK.js";
+import "./chunk-YRSZPVMB.js";
+import "./chunk-OFXBNFNL.js";
+import "./chunk-3CJLKL6E.js";
+import "./chunk-MNV2QFHW.js";
+import "./chunk-PVOWHIND.js";
+import "./chunk-PXKCZB2I.js";
+export {
+  BareRuntime,
+  STATIC_RELEASE_BASE
+};