symfony 3.4 设置 prod 环境

Posted

技术标签:

【中文标题】symfony 3.4 设置 prod 环境【英文标题】:symfony 3.4 set prod environment 【发布时间】:2018-09-23 13:43:28 【问题描述】:

我将 symfony 2.8 升级到 3.4

升级并上传到 mydomain.com 中的生产服务器后?我检查了模式,它是开发而不是产品。

这是我的Htacces:

# Use the front controller as index file. It serves as fallback solution when
# every other rewrite/redirect fails (e.g. in an aliased environment without
# mod_rewrite). Additionally, this reduces the matching process for the
# startpage (path "/") because otherwise Apache will apply the rewritting rules
# to each configured DirectoryIndex file (e.g. index.php, index.html, index.pl).
DirectoryIndex app.php

AddType application/x-httpd-php .php5 .phar

<IfModule mod_rewrite.c>
    RewriteEngine On

    RewriteBase /


    RewriteRule ^web/(.+)$ /$1 [L,NC]



    # Determine the RewriteBase automatically and set it as environment variable.
    # If you are using Apache aliases to do mass virtual hosting or installed the
    # project in a subdirectory, the base path will be prepended to allow proper
    # resolution of the app.php file and to redirect to the correct URI. It will
    # work in environments without path prefix as well, providing a safe, one-size
    # fits all solution. But as you do not need it in this case, you can comment
    # the following 2 lines to eliminate the overhead.
    RewriteCond %REQUEST_URI::$1 ^(/.+)/(.*)::\2$
    RewriteRule ^(.*) - [E=BASE:%1]

    # Redirect to URI without front controller to prevent duplicate content
    # (with and without `/app.php`). Only do this redirect on the initial
    # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
    # endless redirect loop (request -> rewrite to front controller ->
    # redirect -> request -> ...).
    # So in case you get a "too many redirects" error or you always get redirected
    # to the startpage because your Apache does not expose the REDIRECT_STATUS
    # environment variable, you have 2 choices:
    # - disable this feature by commenting the following 2 lines or
    # - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
    #   following RewriteCond (best solution)
    RewriteCond %ENV:REDIRECT_STATUS ^$
    RewriteRule ^app\.php(/(.*)|$) %ENV:BASE/$2 [R=301,L]

    # If the requested filename exists, simply serve it.
    # We only want to let Apache serve files and not directories.
    RewriteCond %REQUEST_FILENAME -f
    RewriteRule .? - [L]

    # Rewrite all other queries to the front controller.
    RewriteRule .? %ENV:BASE/app.php [L]
</IfModule>

<IfModule !mod_rewrite.c>
    <IfModule mod_alias.c>
        # When mod_rewrite is not available, we instruct a temporary redirect of
        # the startpage to the front controller explicitly so that the website
        # and the generated links can still be used.
        RedirectMatch 302 ^/$ /app.php/
        # RedirectTemp cannot be used instead
    </IfModule>
</IfModule>

这是 apapche vhost

<VirtualHost *:8080>
  DocumentRoot "/home/app/symfony"
  ServerName app.com
  ServerAlias  www.app.com
  <Directory "/home/app/symfony">
    allow from all
    Options +Indexes
    AllowOverride All
    Require all granted
  </Directory>
</VirtualHost>

我添加 SetEnv SYMFONY_ENV 产品 允许所有人 选项+索引 允许覆盖所有 要求所有授予

但仍然在 mydomain.com/ 中看到 dev - 如何切换到 prod?

在探查器中:

Symfony 配置 3.4.8 Symfony 版本 应用程序 应用名称 开发者 环境

请求标头: APP_ENV “产品”

SYMFONY_ENV “产品”

我也清除了缓存:

rm -rf var/cache/*;

rm -rf var/logs/*

php bin/console 缓存:清除 --no-warmup --env=prod

php bin/console 缓存:清除 --no-warmup --env=dev

好的找到解决方案 - 简单的错误 - apache vhost 设置为 symfony/ 而不是 symfony/web/ - 如果我更改为 web 它可以工作。

【问题讨论】:

你的问题是什么? 尝试清除缓存。 你如何“在 mydomain.com 中看到 dev”? 你能粘贴你的app.php文件吗? 我看到收费栏,我看到 app_dev.php 文件被使用,我看到 enn: dev 在工具栏/配置中 【参考方案1】:

尝试安装composer require symfony/dotenv,然后在生产服务器上运行composer install --no-dev --optimize-autoloaderphp bin/console cache:clear --env=prod --no-debug

【讨论】:

另外,在安装 symfony/dotenv 之后,您可能需要在项目的根目录中编辑 .env(确保 env 设置为 prod)。

以上是关于symfony 3.4 设置 prod 环境的主要内容,如果未能解决你的问题,请参考以下文章

symfony2.7 prod环境部署的几个问题

Symfony 3 有 1 个虚拟主机和 2 个环境

如何强制 https 用于 prod 但 http 用于开发环境?

Symfony 为不同的环境(产品、测试、开发)使用不同的学说夹具

Symfony 3.4 功能测试

为啥在 prod mod 的 symfony 5.3 中出现 503 错误,而在 dev mod 中却没有