CremindDeployment Types
Choosing local, server, or custom — how the installer sets HOST, APP_URL, and CORS so Cremind is reachable the way you intend.
Both installers ask how Cremind will be reached. The deployment type you pick sets the listen host, the public app URL, and the allowed CORS origins in the rendered .env. Get this right and the backend is reachable exactly where you intend — and nowhere you don't.
The three types
| Deployment | What it sets | When to pick it |
|---|---|---|
| local | HOST=127.0.0.1. Only this machine can reach the backend. | Single-user desktop install. |
| server | HOST=0.0.0.0, APP_URL=http://<your-host>:1112, CORS allows your host. | Multi-machine setup; pass your public IP or domain. |
| custom (advanced) | You set HOST, APP_URL, CORS_ALLOWED_ORIGINS, and the Setup Wizard preset yourself. | Inside containers, behind reverse proxies, or anywhere the local/server presets don't fit. |
local
The default for a single-user install. The backend binds to 127.0.0.1, so only the machine it's installed on can reach it. Nothing else is required — no host flag, no CORS configuration.
server
For reaching Cremind from other machines. The installer binds to 0.0.0.0 and sets APP_URL and the CORS allow-list from the host you give it. Provide your public IP or domain with the host flag:
curl -fsSL https://cremind.io/install.sh | bash -s -- --deployment server --host cremind.example.comiwr -useb https://cremind.io/install.ps1 | iex; cremind-install -Deployment server -AppHost cremind.example.comA server deployment binds to 0.0.0.0 and is reachable from your network. Make sure you understand who can reach the host, and put it behind appropriate network controls before exposing it.
custom (advanced)
When neither preset fits — inside containers, behind a reverse proxy, or any non-standard topology — pick custom and set each field yourself. The relevant flags are:
| Field | sh flag | ps1 flag |
|---|---|---|
Listen host (HOST) | --listen-host | -ListenHost |
Public URL (APP_URL) | --public-url | -PublicUrl |
Allowed origins (CORS_ALLOWED_ORIGINS) | --allowed-origins | -AllowedOrigins |
Setup Wizard preset (SETUP_WIZARD_ENV) | --wizard-preset | -WizardPreset |
See Installer flags for the complete reference.
container is a deprecated alias
container is accepted as a deprecated alias for custom (with container-friendly defaults) for one release. New scripts should use custom directly.
How this relates to install mode
Deployment type (how Cremind is reached) is independent of install mode (Docker vs native — how the agent runs). You answer both during install: the installer asks the mode first, then the deployment type. Either prompt can be skipped with a flag for unattended installs.