Plugin Surfaces (Python Apps, Node.js Apps)

Updated Nov 17, 2026 Markdown

When the operator has activated the matching plugin, additional sidebar items appear. Both use the same upload-first deploy pipeline: upload a zip / tar.gz of your project (or point at a server path under /home/{user}/), the analyzer detects framework / entry point / package manager, then a Server-Sent Events stream walks you through deploy in real time. A server-path deploy copies exactly the folder that was checked: if a folder on that path is replaced by a link while the deploy starts, it stops with "The source folder is not a plain folder (a link stands on its path)."; a name on that path renamed while the path is being checked is refused before the deploy starts with "The source path changed while it was being checked …" — start the deploy again.

If you don't see these entries, the operator has not enabled the plugin on this server.

Both surfaces bind the app to a domain, and that domain has to be one you already hold — your primary domain, an addon domain or a subdomain you created. Anything else is refused with Domain ... is not registered under account ...; add the domain under Domains first.

An app's environment variables are saved as a whole set: when they cannot be read, the tab shows an error state with a Retry button and Save stays off, since saving would replace every stored variable with the ones on screen. The files the panel writes for an app (.env, gunicorn.conf.py, the skeleton files of a new app, the log files in your log folder) must be plain files: when one of those names is a link or a folder you created in its place, the save or the create is refused and the entry is left as it is, the Logs tab shows no lines for such a name, and a deploy stops when the app folder's name is a link. A deploy's media folder is always created under the app folder.

Python Apps

  • Supported frameworks: Django, Flask, FastAPI, Pyramid, Bottle, raw WSGI/ASGI
  • Entrypoint auto-detection: wsgi.py → asgi.py → app.py → main.py (in that priority)
  • Server path analysis: a file or folder whose name leads out of your home (a link such as requirements.txt pointing elsewhere) counts as absent; links that stay inside your home work as usual
  • Virtualenv path: /home/{user}/.python-apps/{appname}/venv/
  • Server runtime:
    • WSGI apps run under gunicorn
    • ASGI apps run under uvicorn
  • Available Python versions: typically 3.10, 3.11, 3.12 (operator-defined)
  • App URL: your primary domain root (https://your-domain.com/) or a chosen subdomain
  • Restart: Apps → {name} → Restart button — takes 2–5 seconds; existing requests finish
  • Logs: the app's Logs tab shows gunicorn's own error and access logs ({app}-error.log, {app}-access.log in your log folder); the web server's lines for the app's domain — every visit, also the ones the app never answered (a 502 while it is down) — are on the Logs page under that domain

Node.js Apps

  • Supported frameworks: Express, Fastify, NestJS, Next.js, Koa, raw HTTP servers
  • Entrypoint auto-detection: package.json → main, then index.js, then server.js
  • node_modules path: /home/{user}/.node-apps/{appname}/node_modules/
  • Package managers supported: npm, pnpm, yarn (auto-detected from lockfile)
  • Available Node versions: typically 18, 20, 22 (operator-defined)
  • Cluster mode: optional multi-instance (PM2-style) — set worker count in app settings
  • Hot reload: dev mode streams file-change events over SSE
  • Restart: identical to Python Apps — 2–5 seconds
  • Logs: on the app's Logs tab, stdout and stderr are the app's own output; Access Log and Error Log are the web server's lines for the app's domain — the same {domain}-access.log / {domain}-error.log the Logs page shows
Still Need Help?

Our support team is here around the clock for anything you can't find above.