What Invokara checks for you
On every start, and in the Files tab, your project is analysed. Anything that could stop it from working is shown with an explanation and the fix:
| Situation | What we do |
|---|---|
| Project in a subfolder, several projects in the zip | We run the right folder and tell you about the others |
ecosystem.config.js (pm2) or Procfile with several programs | All started together |
| TypeScript project | npm run build before starting, or the .ts file is run directly |
node_modules, venv, __pycache__ in the zip | Ignored and reinstalled for the server |
Web server on localhost / 127.0.0.1 | Warning + HOST=0.0.0.0 |
| Port in the code different from the web panel port | Warning with the port to set |
| Web panel not answering 30 s after starting | Explanation in the console |
Variables from .env.example missing | List of variables to add |
Public URL or OAuth callback on localhost | The exact address to use (and to register on Discord) |
Windows paths (C:\…, \), CRLF line endings | File and line to fix |
Different letter case (./Commands for a commands folder) | File and line to fix: Linux is case-sensitive |
| Discord token written in the code | Warning: move it to Variables and regenerate it |
| Newer Node version required, wrong language picked | The setting to change in Settings |
No package.json / requirements.txt | How to create it |