Q & A

After Go Live!, deploy can succeed while the live URL still shows a blank page or directory listing. Robotron auto-detects back-end apps (PHP/Laravel, Python/Django, WordPress, etc.) from markers like composer.json or manage.py at the project root, and uses static Apache hosting for everything else.

Back-end app? Open the app root folder — the one that contains composer.json, artisan, manage.py, requirements.txt, or wp-config.php — not a parent or subfolder. Click Go Live! again; Robotron deploys back-end stacks to Docker.

Static front-end or still stuck? Send this prompt to your AI editor:

Prepare this project for Robotron Go Live (VS Code/Cursor).

Back-end (Laravel/PHP, Python/Django, WordPress, PrestaShop): keep normal app layout at this folder root (composer.json, artisan, manage.py, requirements.txt, or wp-config.php). Robotron auto-detects and deploys to Docker — do not convert to static HTML.

Static front-end: put index.html at the project root with css/, js/, and images/ beside it; relative asset paths (./css/style.css); ship ready-to-serve files — Robotron static hosting does not run npm install or npm run build.

Do not start a new project. Fix whatever causes a blank page or directory listing after deploy.

Tip: copy the prompt above, paste it into Cursor or VS Code chat, let the AI prepare this project for Go Live, then click Go Live! again.