为什么我在将 Symfony 4 应用程序部署到 Heroku 时遇到问题？

Question

我正在尝试将我的 Symfony 4 应用程序部署到 Heroku，但显然遇到了一些问题。

我第一次遇到“403 Forbidden”错误是因为我的 Procfile 中没有设置文档根目录。 我对此的回答是，在阅读了我可以找到的其他问题和答案后，使用以下任何一种：

web: $(composer config bin-dir)/heroku-php-apache2 public/
web: bin/heroku-php-apache2 public/
web: vendor/bin/heroku-php-apache2 public/
web: vendor/bin/heroku-php-apache2 /public/

他们都返回了不同类型的“500 内部服务器错误”页面——其中大部分都说类似于Request exceeded the limit of 10 internal redirects due to probable configuration error.

这让我想到了我的 public/.htaccess 文件中的一些问题。

移除 cmets 后，它看起来像这样：

# Use the front controller as index file. It serves as a 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
# start page (path "/") because otherwise Apache will apply the rewriting rules
# to each configured DirectoryIndex file (e.g. index.php, index.html, index.pl).
DirectoryIndex app.php

# By default, Apache does not evaluate symbolic links if you did not enable this
# feature in your server configuration. Uncomment the following line if you
# install assets as symlinks or if you experience problems related to symlinks
# when compiling LESS/Sass/CoffeScript assets.
# Options FollowSymlinks

# Disabling MultiViews prevents unwanted negotiation, e.g. "/app" should not resolve
# to the front controller "/app.php" but be rewritten to "/app.php/app".
<IfModule mod_negotiation.c>
    Options -MultiViews
</IfModule>

<IfModule mod_rewrite.c>
    RewriteEngine On

    # 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]

    # Sets the HTTP_AUTHORIZATION header removed by Apache
    RewriteCond %{HTTP:Authorization} .
    RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # 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 start page 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}/$1 [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 start page 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>

这确实很奇怪，因为我没有 public/app.php 文件 - 但是，将其替换为 index.php 似乎也无法解决问题。

我真的不知道还能尝试什么，非常感谢您的帮助。

Answer 1

在我的情况下，我没有添加路线“/”。 Symfony 在没有该路由的本地环境中加载默认页面，但在 heroku 中我们需要添加它！

我显示我的代码供您参考：

class DefaultController extends AbstractController
{
    /**
     * @Route("/", name="default")
     */
    public function ping()
    {
        return $this->json([
            'message' => 'pong'
        ]);
    }
}

Answer 2

如果其他人在尝试部署 Symfony / Symfony 4 应用程序时偶然发现此问题，我必须采取以下步骤来解决该问题：

• 我的 .htaccess 文件已经过时并且仍然引用旧的 Symfony 3 app.php。我必须做的是删除它并通过composer require symfony/apache-pack 获取新的
• 此时，我仍然收到 500 错误，而且 Heroku 日志没有显示任何有用的信息。这是因为 Heroku 要求您将内容记录到 php://stderr 以使它们正确登录到 CLI 和 Web 界面。因此，我必须修改我的 config/packages/prod/monolog.yaml 文件以使 nested 处理程序如下所示：path: "php://stderr"

就我而言，第二个问题原来是我忘记在我的 postinstall 脚​​本中运行 node_modules/.bin/encore production - 但只是将日志重定向到 php://stderr 应该可以为任何人指明正确的方向。