This guide provides bulletproof startup scripts with zero dependencies.
Just double-click:
QUICK_START.bat
This script:
- Automatically stops any process using port 5010
- Starts the controller
- Shows clear status messages
- Works every single time
Right-click and "Run as Administrator":
SIMPLE_AUTO_START_SETUP.bat
This creates a Windows Task Scheduler entry that runs on login.
- You restart Windows
- You log in
- Controller starts automatically (hidden in background)
- Dashboard available at http://127.0.0.1:5010
schtasks /Query /TN "Local Nexus Controller"schtasks /Delete /TN "Local Nexus Controller" /FSolution: The scripts now handle this automatically. Every startup:
- Checks port 5010
- Stops any conflicting process
- Waits briefly
- Starts cleanly
Check if Python is installed:
python --versionIf not installed:
- Download from https://www.python.org/downloads/
- During installation, check "Add Python to PATH"
The startup script automatically:
- Checks for
.venvfolder - Uses it if available
- Falls back to system Python if not
If you get "scripts are disabled" error:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUserQUICK_START.bat- Simple manual startupstart.bat- Alternative manual startuprun.ps1- PowerShell manual startup
SIMPLE_AUTO_START_SETUP.bat- One-click auto-start setuptools/auto_start_controller.ps1- The script that runs on boot
All auto-start activity is logged to:
data/logs/auto-start.log
Check this file if something goes wrong.
1. Changes to project directory
2. Calls run.ps1
3. run.ps1 checks port 5010
4. run.ps1 stops conflicts
5. run.ps1 creates/uses venv
6. run.ps1 starts controller
1. Windows loads
2. You log in
3. Task Scheduler triggers
4. Runs tools/auto_start_controller.ps1
5. Script checks port
6. Script stops conflicts
7. Script finds Python
8. Script starts controller
9. Everything logged to data/logs/auto-start.log
- No complex dependencies
- No script-calling-script chains
- Absolute paths everywhere
- Clear error messages
- Always checks port first
- Always stops conflicts
- Never fails due to "port in use"
- Everything logged to file
- Easy to diagnose issues
- Timestamps on all events
- Tries venv Python first
- Falls back to system Python
- Clear error if neither found
QUICK_START.batExpected output:
Checking for port conflicts and starting controller...
✓ Port 5010 is available
(or)
Stopping process ... (PID: 1234)
✓ Process stopped
[Controller starts]
- Run
SIMPLE_AUTO_START_SETUP.batas Administrator - Check task created:
schtasks /Query /TN "Local Nexus Controller"
- Test the task:
schtasks /Run /TN "Local Nexus Controller"
- Check log:
type data\logs\auto-start.log
- Restart Windows
- Log in
- Wait 10 seconds
- Open browser: http://127.0.0.1:5010
- Check log:
data\logs\auto-start.log
You now have two simple options:
- Manual: Double-click
QUICK_START.bat - Automatic: Run
SIMPLE_AUTO_START_SETUP.batonce (as Admin)
Both handle port conflicts automatically. Both work reliably. No complex setup required.