Find framework reference pages for handlers, routes, middleware, modules, database, views, and security.

Reference search

Results for "production"

Reference results link to the matching section. Follow its prerequisites before using a code extract.

From the matching guide

Development And Production

With APP_ENV=production , the default route cache uses cache/routes.php . Incoming requests check the route directory periodically; the default refresh interval is 30 seconds. New files may not become visible until the next refresh. Outside...

php coriander routes:list

Development And Production

With APP_ENV=production , the default route cache uses cache/routes.php . Incoming requests check the route directory periodically; the default refresh interval is 30 seconds. New files may not become visible until the next refresh. Outside...

Production Checklist

Deploy tested app-owned code together with the framework version it supports. A successful core update alone is not a successful application migration.

Inspect Routes

...It uses current files even when production has a cached route map. It does not execute handlers/middleware or change the cache.

Migration safety notes

...Keep migrations immutable in shared/staging/production environments. Each migration's changes and history record share a transaction where the database supports it. With SQLite, a failure rolls back both. MySQL DDL statements can commit imp...

SQLite And MySQL

SQLite is good for: local learning demos small single-server apps tests MySQL is usually better for: multi-user production apps larger data volume managed hosting applications with existing MySQL tooling Keep SQL portable where possible. Wh...

No Connection Or Host 404

...See Production Checklist .

Override Behavior

The 0.4.1 starter defaults to APP_ENV=production and APP_DEBUG=0 . The example above deliberately enables local debugging. Existing .env files are not rewritten on framework updates; choose safe values explicitly for a public deployment. Ex...

Configure Environment

...The 0.4.1 starter defaults to production with debug disabled. On a trusted local machine, explicitly use: Use APP_ENV=production and APP_DEBUG=0 on a public server. Existing environment files are not rewritten by framework updates. If your ...

Create The Schema

...Replace the generated file in database/migrations with this complete migration, keeping its generated filename: The fixed sample row belongs to this learning example, not a recommended production seeding strategy. For MySQL, use id INTEGER ...

Deploy Prebuilt Assets

...Generated JavaScript and production CSS include content fingerprints used by PublicUrl::versionedAsset() . build-tw runs fingerprint-css.js after Tailwind; build-all and build-prod reuse that command. No extra deployment command is needed. ...

Builds, Watchers, And Deployment

...Generated scripts and production CSS carry content fingerprints, so cache URLs change even if timestamps do not. PHP reads a bounded prefix for these versions; unmarked/manual/watch CSS and JavaScript use content hashing. Standard productio...

Debug By Layer

...See Errors And Debugging for checks and Security for safe production error handling.

Cookies, Proxies, And Errors

Use HTTPS in production. TRUSTED_PROXIES accepts trusted IPs/CIDRs; forwarded TLS headers are trusted only for matching peers. Do not trust every proxy just to fix cookie settings. Incoming request URIs now include the origin when a host is...

Prerequisites

...This is not a complete production authentication product: add login throttling, account lifecycle/recovery, session expiry, and appropriate permission checks for your app. Never copy the forum's quick role-login buttons into a real applicat...

Route Smoke Test

...Use an isolated test database and session storage, never your production database. The router test exercises middleware and handlers, not the front controller's parsing or HTTP emission; add an HTTP check for those boundaries. For JSON inte...

Before Deployment

...Production route maps refresh automatically, normally within 30 seconds; no deploy-time route-build command is required. Keep OPcache timestamp validation enabled or restart PHP workers when replacing PHP files.