nodmix 2026.5.25

package/docs/install/hostinger.md

@@ -0,0 +1,98 @@
+---
+summary: "Host Nodmix on Hostinger"
+read_when:
+  - Setting up Nodmix on Hostinger
+  - Looking for a managed VPS for Nodmix
+  - Using Hostinger 1-Click Nodmix
+title: "Hostinger"
+---
+
+Run a persistent Nodmix Gateway on [Hostinger](https://www.hostinger.com/nodmix) via a **1-Click** managed deployment or a **VPS** install.
+
+## Prerequisites
+
+- Hostinger account ([signup](https://www.hostinger.com/nodmix))
+- About 5-10 minutes
+
+## Option A: 1-Click Nodmix
+
+The fastest way to get started. Hostinger handles infrastructure, Docker, and automatic updates.
+
+<Steps>
+  <Step title="Purchase and launch">
+    1. From the [Hostinger Nodmix page](https://www.hostinger.com/nodmix), choose a Managed Nodmix plan and complete checkout.
+
+    <Note>
+    During checkout you can select **Ready-to-Use AI** credits that are pre-purchased and integrated instantly inside Nodmix -- no external accounts or API keys from other providers needed. You can start chatting right away. Alternatively, provide your own key from Anthropic, OpenAI, Google Gemini, or xAI during setup.
+    </Note>
+
+  </Step>
+
+  <Step title="Select a messaging channel">
+    Choose one or more channels to connect:
+
+    - **WhatsApp** -- scan the QR code shown in the setup wizard.
+    - **Telegram** -- paste the bot token from [BotFather](https://t.me/BotFather).
+
+  </Step>
+
+  <Step title="Complete installation">
+    Click **Finish** to deploy the instance. Once ready, access the Nodmix dashboard from **Nodmix Overview** in hPanel.
+  </Step>
+
+</Steps>
+
+## Option B: Nodmix on VPS
+
+More control over your server. Hostinger deploys Nodmix via Docker on your VPS and you manage it through the **Docker Manager** in hPanel.
+
+<Steps>
+  <Step title="Purchase a VPS">
+    1. From the [Hostinger Nodmix page](https://www.hostinger.com/nodmix), choose an Nodmix on VPS plan and complete checkout.
+
+    <Note>
+    You can select **Ready-to-Use AI** credits during checkout -- these are pre-purchased and integrated instantly inside Nodmix, so you can start chatting without any external accounts or API keys from other providers.
+    </Note>
+
+  </Step>
+
+  <Step title="Configure Nodmix">
+    Once the VPS is provisioned, fill in the configuration fields:
+
+    - **Gateway token** -- auto-generated; save it for later use.
+    - **WhatsApp number** -- your number with country code (optional).
+    - **Telegram bot token** -- from [BotFather](https://t.me/BotFather) (optional).
+    - **API keys** -- only needed if you did not select Ready-to-Use AI credits during checkout.
+
+  </Step>
+
+  <Step title="Start Nodmix">
+    Click **Deploy**. Once running, open the Nodmix dashboard from the hPanel by clicking on **Open**.
+  </Step>
+
+</Steps>
+
+Logs, restarts, and updates are managed directly from the Docker Manager interface in hPanel. To update, press on **Update** in Docker Manager and that will pull the latest image.
+
+## Verify your setup
+
+Send "Hi" to your assistant on the channel you connected. Nodmix will reply and walk you through initial preferences.
+
+## Troubleshooting
+
+**Dashboard not loading** -- Wait a few minutes for the container to finish provisioning. Check the Docker Manager logs in hPanel.
+
+**Docker container keeps restarting** -- Open Docker Manager logs and look for configuration errors (missing tokens, invalid API keys).
+
+**Telegram bot not responding** -- Send your pairing code message from Telegram directly as a message inside your Nodmix chat to complete the connection.
+
+## Next steps
+
+- [Channels](/channels) -- connect Telegram, WhatsApp, Discord, and more
+- [Gateway configuration](/gateway/configuration) -- all config options
+
+## Related
+
+- [Install overview](/install)
+- [VPS hosting](/vps)
+- [DigitalOcean](/install/digitalocean)

package/docs/install/index.md

@@ -0,0 +1,221 @@
+---
+summary: "Install Nodmix - installer script, npm/pnpm/bun, from source, Docker, and more"
+read_when:
+  - You need an install method other than the Getting Started quickstart
+  - You want to deploy to a cloud platform
+  - You need to update, migrate, or uninstall
+title: "Install"
+---
+
+## System requirements
+
+- **Node 24** (recommended) or Node 22.19+ - the installer script handles this automatically
+- **macOS, Linux, or Windows** - both native Windows and WSL2 are supported; WSL2 is more stable. See [Windows](/platforms/windows).
+- `pnpm` is only needed if you build from source
+
+## Recommended: installer script
+
+The fastest way to install. It detects your OS, installs Node if needed, installs Nodmix, and launches onboarding.
+
+<Tabs>
+  <Tab title="macOS / Linux / WSL2">
+    ```bash
+    curl -fsSL https://nodmix.ai/install.sh | bash
+    ```
+  </Tab>
+  <Tab title="Windows (PowerShell)">
+    ```powershell
+    iwr -useb https://nodmix.ai/install.ps1 | iex
+    ```
+  </Tab>
+</Tabs>
+
+To install without running onboarding:
+
+<Tabs>
+  <Tab title="macOS / Linux / WSL2">
+    ```bash
+    curl -fsSL https://nodmix.ai/install.sh | bash -s -- --no-onboard
+    ```
+  </Tab>
+  <Tab title="Windows (PowerShell)">
+    ```powershell
+    & ([scriptblock]::Create((iwr -useb https://nodmix.ai/install.ps1))) -NoOnboard
+    ```
+  </Tab>
+</Tabs>
+
+For all flags and CI/automation options, see [Installer internals](/install/installer).
+
+## Alternative install methods
+
+### Local prefix installer (`install-cli.sh`)
+
+Use this when you want Nodmix and Node kept under a local prefix such as
+`~/.nodmix`, without depending on a system-wide Node install:
+
+```bash
+curl -fsSL https://nodmix.ai/install-cli.sh | bash
+```
+
+It supports npm installs by default, plus git-checkout installs under the same
+prefix flow. Full reference: [Installer internals](/install/installer#install-clish).
+
+Already installed? Switch between package and git installs with
+`nodmix update --channel dev` and `nodmix update --channel stable`. See
+[Updating](/install/updating#switch-between-npm-and-git-installs).
+
+### npm, pnpm, or bun
+
+If you already manage Node yourself:
+
+<Tabs>
+  <Tab title="npm">
+    ```bash
+    npm install -g nodmix@latest
+    nodmix onboard --install-daemon
+    ```
+
+    <Note>
+    The hosted installer clears npm freshness filters such as `min-release-age`
+    for the Nodmix package install. If you install manually with npm, your own
+    npm policy still applies.
+    </Note>
+
+  </Tab>
+  <Tab title="pnpm">
+    ```bash
+    pnpm add -g nodmix@latest
+    pnpm approve-builds -g
+    nodmix onboard --install-daemon
+    ```
+
+    <Note>
+    pnpm requires explicit approval for packages with build scripts. Run `pnpm approve-builds -g` after the first install.
+    </Note>
+
+  </Tab>
+  <Tab title="bun">
+    ```bash
+    bun add -g nodmix@latest
+    nodmix onboard --install-daemon
+    ```
+
+    <Note>
+    Bun is supported for the global CLI install path. For the Gateway runtime, Node remains the recommended daemon runtime.
+    </Note>
+
+  </Tab>
+</Tabs>
+
+<Accordion title="Troubleshooting: sharp build errors (npm)">
+  If `sharp` fails due to a globally installed libvips:
+
+```bash
+SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g nodmix@latest
+```
+
+</Accordion>
+
+### From source
+
+For contributors or anyone who wants to run from a local checkout:
+
+```bash
+git clone https://github.com/nodmix/nodmix.git
+cd nodmix
+pnpm install && pnpm build && pnpm ui:build
+pnpm link --global
+nodmix onboard --install-daemon
+```
+
+Or skip the link and use `pnpm nodmix ...` from inside the repo. See [Setup](/start/setup) for full development workflows.
+
+### Install from GitHub main
+
+```bash
+npm install -g github:nodmix/nodmix#main
+```
+
+### Containers and package managers
+
+<CardGroup cols={2}>
+  <Card title="Docker" href="/install/docker" icon="container">
+    Containerized or headless deployments.
+  </Card>
+  <Card title="Podman" href="/install/podman" icon="container">
+    Rootless container alternative to Docker.
+  </Card>
+  <Card title="Nix" href="/install/nix" icon="snowflake">
+    Declarative install via Nix flake.
+  </Card>
+  <Card title="Ansible" href="/install/ansible" icon="server">
+    Automated fleet provisioning.
+  </Card>
+  <Card title="Bun" href="/install/bun" icon="zap">
+    CLI-only usage via the Bun runtime.
+  </Card>
+</CardGroup>
+
+## Verify the install
+
+```bash
+nodmix --version      # confirm the CLI is available
+nodmix doctor         # check for config issues
+nodmix gateway status # verify the Gateway is running
+```
+
+If you want managed startup after install:
+
+- macOS: LaunchAgent via `nodmix onboard --install-daemon` or `nodmix gateway install`
+- Linux/WSL2: systemd user service via the same commands
+- Native Windows: Scheduled Task first, with a per-user Startup-folder login item fallback if task creation is denied
+
+## Hosting and deployment
+
+Deploy Nodmix on a cloud server or VPS:
+
+<CardGroup cols={3}>
+  <Card title="VPS" href="/vps">Any Linux VPS</Card>
+  <Card title="Docker VM" href="/install/docker-vm-runtime">Shared Docker steps</Card>
+  <Card title="Kubernetes" href="/install/kubernetes">K8s</Card>
+  <Card title="Fly.io" href="/install/fly">Fly.io</Card>
+  <Card title="Hetzner" href="/install/hetzner">Hetzner</Card>
+  <Card title="GCP" href="/install/gcp">Google Cloud</Card>
+  <Card title="Azure" href="/install/azure">Azure</Card>
+  <Card title="Railway" href="/install/railway">Railway</Card>
+  <Card title="Render" href="/install/render">Render</Card>
+  <Card title="Northflank" href="/install/northflank">Northflank</Card>
+</CardGroup>
+
+## Update, migrate, or uninstall
+
+<CardGroup cols={3}>
+  <Card title="Updating" href="/install/updating" icon="refresh-cw">
+    Keep Nodmix up to date.
+  </Card>
+  <Card title="Migrating" href="/install/migrating" icon="arrow-right">
+    Move to a new machine.
+  </Card>
+  <Card title="Uninstall" href="/install/uninstall" icon="trash-2">
+    Remove Nodmix completely.
+  </Card>
+</CardGroup>
+
+## Troubleshooting: `nodmix` not found
+
+If the install succeeded but `nodmix` is not found in your terminal:
+
+```bash
+node -v           # Node installed?
+npm prefix -g     # Where are global packages?
+echo "$PATH"      # Is the global bin dir in PATH?
+```
+
+If `$(npm prefix -g)/bin` is not in your `$PATH`, add it to your shell startup file (`~/.zshrc` or `~/.bashrc`):
+
+```bash
+export PATH="$(npm prefix -g)/bin:$PATH"
+```
+
+Then open a new terminal. See [Node setup](/install/node) for more details.