apps
|
|
| Panel and API |
https://apps.xvii.network (/api/v1) |
| Apps |
https://<app>.apps.xvii.network (production), https://<app>-<env>.apps.xvii.network |
| Bots |
https://bots.xvii.network/<app id> |
| Nodes |
https://apps.xvii.network/join.sh, agents at wss://apps.xvii.network/agent |
| CI |
https://apps.xvii.network/ci/gitlab.yml, /ci/github.yml |
| CLI |
xvii apps … |
What it does
- Kinds: web, worker, bot (Telegram webhooks), cron, database.
- Releases: the new container starts beside the live one and takes over once healthy; a failure keeps
the last live release; rollback is a new release of an old one.
- Builds on the node, no registry: Dockerfile or Railpack; the last five builds kept.
- Previews for branches and merge requests, gone after their TTL.
- Databases: PostgreSQL, MariaDB, Valkey, Redis, MongoDB with dumps, restores and backups.
- Variables from env plus the app's own, files mounted read-only, volumes.
- Templates: about fifty-five applications pinned to real image tags; instances add their own.
- Compose import and adopting a server's existing projects in place.
- Nodes: instance nodes shared with quotas, teams' own nodes, edge or relay ingress, moves between
nodes.
- Integrations: errors (the DSN), analytics (server-side counting), domains (custom names).
- Logs and per-minute metrics for 30 days.
Limits
apps.apps, apps.memory, apps.cpu, apps.nodes.
Events
app.deployed, app.deploy_failed, app.crashed, cron.failed, bot.webhook_failed, node.online,
node.offline, quota.near_limit, database.backup_failed, database.restored.
Deploy an app · Apps guide ·
Databases · Nodes