[英]Why am I having issues deploying Symfony 4 app to Heroku?
I'm trying to deploy my Symfony 4 app to Heroku and, obviously, encountering some issues with it. 我正在尝试将我的Symfony 4应用程序部署到Heroku,显然,它遇到了一些问题。
I first had the "403 Forbidden" error because the document root had not been set in my Procfile. 我首先遇到“403 Forbidden”错误,因为我的Procfile中没有设置文档根目录。 My answer to that was, after reading other questions and answers I could find around, using any of these:
我的回答是,在阅读了我能找到的其他问题和答案之后,使用以下任何一个:
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/
They all gave back different kinds of "500 Internal Server Error" pages - most of them, saying something along the lines of Request exceeded the limit of 10 internal redirects due to probable configuration error.
他们都回馈了不同类型的“500内部服务器错误”页面 - 其中大多数都说
Request exceeded the limit of 10 internal redirects due to probable configuration error.
, Request exceeded the limit of 10 internal redirects due to probable configuration error.
Which lead me to think about some issue in my public/.htaccess
file instead. 这导致我在我的
public/.htaccess
文件中考虑一些问题。
With comments removed, it looks like this: 删除评论后,它看起来像这样:
# 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>
Which is indeed weird as I have no public/app.php
file - however, swapping that for index.php doesn't seem to fix things either. 这确实很奇怪,因为我没有
public/app.php
文件 - 但是,为index.php交换它似乎也没有解决问题。
I really don't know what else to try, help would be much appreciated. 我真的不知道还有什么可以尝试,非常感谢帮助。
In my case is I did not add the route "/". 在我的情况下,我没有添加路线“/”。 Symfony load default page in local environment without that route, but in heroku we need to add it!
Symfony在没有该路由的本地环境中加载默认页面,但在heroku中我们需要添加它!
I show my code for your reference: 我展示了我的代码供您参考:
class DefaultController extends AbstractController
{
/**
* @Route("/", name="default")
*/
public function ping()
{
return $this->json([
'message' => 'pong'
]);
}
}
In case anyone else stumbles upon this trying to deploy a Symfony / Symfony 4 app, these are the steps I had to take to solve the issue: 如果其他人偶然发现尝试部署Symfony / Symfony 4应用程序,这些是我必须采取的步骤来解决问题:
composer require symfony/apache-pack
composer require symfony/apache-pack
获取新的 php://stderr
to have them properly logged in the CLI and web interface. php://stderr
以便在CLI和Web界面中正确记录它们。 As such, I had to modify my config/packages/prod/monolog.yaml
file to have the nested
handler be like this: path: "php://stderr"
config/packages/prod/monolog.yaml
文件以使nested
处理程序如下所示: path: "php://stderr"
In my case, the second issue turned out being I'd forgotten to run node_modules/.bin/encore production
in my postinstall
script - but just redirecting logging to php://stderr
should point anyone in the right direction. 在我的情况下,第二个问题结果是我忘记在我的
postinstall
脚本中运行node_modules/.bin/encore production
- 但只是将日志重定向到php://stderr
应该指向任何人正确的方向。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.