Repository navigation
Troubleshooting
Start by identifying whether the issue is in Composer/PHP, the generated application bootstrap, a route/controller, or an optional integration. Reproduce the problem with the smallest request or command and consult the app's logs without exposing secrets.
Machinjiri requires PHP ^8.4. Check both php --version and the PHP binary Composer uses. A web server may use a different PHP installation from your terminal.
The installer is a separate global Composer package. Check that it installed successfully and that Composer's global vendor/bin directory is on your PATH.
The framework source checkout does not contain an Artisan script. Change into an application generated by the installer and run the command there.
- Confirm the generated entry point includes the route file.
- Confirm the HTTP method and path match.
- Register the route before the single
Router::dispatch()call. - Check route groups and prefixes.
- Confirm no route cache/configuration is stale if your app enables one.
Check the application's PSR-4 autoload mapping, namespace spelling, filename/class name, and whether Composer's autoloader is loaded.
Check the configured view root, the view name/path convention, file extension, and permissions. The starter example uses resources/views/home.view.php, but the generated app controls lookup configuration.
Confirm the database service is running and reachable, credentials and database name are correct, the PHP driver extension is installed, and the selected driver value matches the configured database. Keep connection errors private in production logs.
Verify the correct environment/configuration loaded, the migration ran against that database, the query filters use the intended column/value, and the app is not reading a different database than the one seeded.
Check that the queue service provider is loaded, the selected driver is configured, and the required queue tables have been initialized when using the database driver. Use the exact instructions from the worker command's help output.
Check optional client packages, required PHP extensions, endpoint reachability, credentials, and provider-side permissions. The framework's class being installed does not guarantee its external service has been configured.
Check request path/method, signature verification configuration, clocks/secret rotation, response status, and idempotency behavior. Avoid placing raw credentials or complete sensitive payloads in logs.
- Reproduce with debug mode only in a local environment.
- In production, return generic error responses and retain details in access-controlled logs.
- Never paste secrets, tokens, session cookies, or personal data into public issues.
- Include PHP/framework versions, the exact command or request, sanitized logs, and a minimal reproduction when reporting a bug.
If the issue appears to be a framework vulnerability, follow the private reporting instructions in the security policy.
Machinjiri Docs
- Home
- Learn
- Build
-
Tutorials
- Routing
- Controllers and Middleware
- Views and Templates
- Database ORM
- Eloquent Database ORM
- Errors and Exceptions
- Forms and Validation
- Http
- Events and Logging
- Services and DI
- Security
- Authentication
- Caching
- File System
- Date and Time
- Debugging
- Queue and Jobs
- Task Scheduling
- Transport (Mail, SMS)
- LDAP
- Notifications
- Webhooks
- UUID Generations
- Terminal
- Helper Function
- Reference