To configure the base URL in a Yii2 application, modify the 'urlManager' component in config/web.php by setting 'baseUrl' to your desired path. 1. Set 'baseUrl' under 'urlManager' to match your app's root path (e.g., '/myapp'). 2. Enable clean URLs with 'enablePrettyUrl' and disable script name in URLs with 'showScriptName'. 3. If assets fail to load, ensure asset bundles use '$baseUrl = '@web'' and '@webroot' points to the correct directory. 4. Use environment variables (like BASE_URL) for flexible deployment across environments. 5. Verify .htaccess settings for Apache servers using pretty URLs and clear runtime cache after changes. This ensures proper routing, asset loading, and environment adaptability.

When setting up a Yii application, especially when moving from a development environment to production or organizing your site structure, you may need to configure the base URL. The base URL is essentially the root address that your application uses to generate links and handle routing correctly.

Here’s how to do it properly, depending on your setup and version of Yii (we'll cover Yii2 specifically, which is the most widely used version at the time of writing).

Understanding Base URL in Yii

In Yii2, the base URL is usually determined automatically based on where your entry script (index.php) is located. However, sometimes you’ll want to set it manually—especially if your app lives in a subdirectory or behind a proxy.

You don’t always have to change this, but knowing where to find it and how to adjust it can save you headaches later.

Setting Base URL in urlManager (Most Common Method)

The primary place to configure the base URL behavior is in the urlManager component of your application configuration.

Open your config file—usually found at config/web.php for web applications—and look for the 'urlManager' section. If it's not there, you can add it inside the 'components' array.

'components' => [
    'urlManager' => [
        'baseUrl' => '/myapp',
        'enablePrettyUrl' => true,
        'showScriptName' => false,
    ],
],

• baseUrl – This tells Yii what path your app is running under.
• enablePrettyUrl – Enables clean URLs (e.g., /site/about instead of index.php?r=site/about)
• showScriptName – Whether to show index.php in URLs

For example, if your site is accessible via https://example.com/myapp/, then setting 'baseUrl' => '/myapp' will ensure all generated URLs start with that prefix.

This affects things like Yii::$app->urlManager->createUrl() and $this->redirect() calls.

Handling Base URL in Asset Bundles

If your assets (CSS, JS) are not loading properly after changing the base URL, it might be because asset bundles are using incorrect paths.

To fix this, you can explicitly set the baseUrl in your asset bundles:

class AppAsset extends AssetBundle
{
    public $basePath = '@webroot';
    public $baseUrl = '@web';

    public $css = [
        'css/site.css',
    ];
}

• @web resolves to the correct web-accessible directory, factoring in the base URL.
• You generally don't need to change this unless you're dealing with symlinks or custom folder structures.

Also, make sure that your @webroot alias points to the right physical directory containing your assets. It should point to the same directory as your index.php.

Using Environment Variables for Flexibility

Instead of hardcoding values like /myapp, consider using environment variables so your code can adapt across environments (local, staging, production):

In your .env file:

BASE_URL=/myapp

Then in your config:

'components' => [
    'urlManager' => [
        'baseUrl' => getenv('BASE_URL'),
        ...
    ],
],

This makes deployment easier and reduces the risk of misconfiguration.

Common Pitfalls and Tips

• Incorrect .htaccess: If you're using Apache and pretty URLs, make sure your .htaccess file allows URL rewriting and that AllowOverride is enabled.
• Caching issues: After making changes to urlManager, clear your cache by deleting contents from the runtime/cache folder.
• Subdomains vs subpaths: If your app runs on a subdomain (like app.example.com), you probably don’t need to set baseUrl. But if it's under a subpath (example.com/app), then setting baseUrl becomes essential.
• Use Yii::getAlias('@web') to check the current base URL: In controllers or views, use this helper to debug or build URLs dynamically.

That’s about it — configuring the base URL in Yii is straightforward once you know where to look. Just remember to test your links and asset paths after making any changes.

The above is the detailed content of How do I configure the base URL for my Yii application?. For more information, please follow other related articles on the PHP Chinese website!