使用php artisan serve与localhost/myproject/public访问的差异及问题排查

Hey there! Let's break down exactly what's different between these two ways of running your Laravel project, and why you're hitting issues when accessing it directly.

Core Differences #

• Underlying Server Software:

  • php artisan serve spins up PHP's built-in development web server. It's a lightweight, single-purpose tool meant just for local development, with zero extra configuration needed to work with Laravel out of the box.
  • Accessing via localhost/myproject/public uses your system's full-fledged web server (usually Apache or Nginx) — the same type you'd deploy to production. These servers require specific setup to handle Laravel's routing and file structure properly.

• Routing & Front Controller Handling:

  • The PHP built-in server automatically routes every incoming request through Laravel's front controller (public/index.php) when you run artisan serve — it's hardcoded to play nice with Laravel's structure.
  • When accessing directly via your web server, Apache/Nginx needs explicit rules to send non-static requests (like your app's custom routes) to index.php. If these rules are missing or misconfigured, the server will try to serve route URLs as physical files, leading to broken functionality or 404 errors.

• Document Root Mapping:

  • php artisan serve treats your project's root directory as the base, but internally serves files exclusively from the public folder — it handles this mapping automatically so you don't have to think about it.
  • When accessing via localhost/myproject/public, your web server's document root is likely set to your main htdocs or www folder (where myproject lives). This can mess up asset paths generated by Laravel's asset() helper, and cause the server to fail loading dependencies from the vendor folder correctly.

Why Direct Access Breaks Your Code #

The most common reasons your code works with artisan serve but fails when accessing directly are:

1. Missing/Inactive URL Rewrite Rules:

   • Apache: If mod_rewrite isn't enabled, or your server's AllowOverride setting is set to None, the .htaccess file in your public folder (which tells Apache to route requests to index.php) won't be respected.
   • Nginx: If you haven't added the try_files $uri $uri/ /index.php?$query_string; rule to your server block, non-static requests will never reach Laravel's front controller.

2. Incorrect Document Root:

   • If your web server's document root is set to myproject instead of myproject/public, Laravel's secure file structure gets bypassed. The server will try to load files from the project root, leading to missing dependencies or broken asset links.

3. Mismatched Environment Configuration:

   • If your .env file has APP_URL=http://localhost:8000 (the default for artisan serve), but you're accessing the app via http://localhost/myproject/public, any code relying on APP_URL (like link generation or API endpoints) will point to the wrong location, causing failures.

Quick Fixes to Get Direct Access Working #

• Set the Correct Document Root: Configure your Apache/Nginx to point directly to your project's public folder, not the project root.
• Enable URL Rewrites:
  • For Apache: Enable mod_rewrite (use a2enmod rewrite on Linux) and set AllowOverride All in your virtual host or directory configuration.
  • For Nginx: Add the try_files rule mentioned earlier to your server block.
• Update .env: Change APP_URL to match your direct access URL (e.g., http://localhost/myproject/public).

内容的提问来源于stack exchange，提问作者Blues Clues