要耐心,我是symfony框架的新手 如果我跑:
php app / console server:运行
一切正常
如果我去:
一切正常
如果我去:
我收到了这个错误
my project.conf
<VirtualHost *:80>
ServerName myproject.com
ServerAlias www.myproject.com
DocumentRoot /home/whisher/public_html/myproject/web
<Directory /home/whisher/public_html/myproject/web>
# enable the .htaccess rewrites
AllowOverride All
Order allow,deny
Allow from All
</Directory>
ErrorLog /var/log/apache2/project_error.log
CustomLog /var/log/apache2/project_access.log combined
</VirtualHost>
请帮帮我吗?
# 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
<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]
# 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}/$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 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>
答案 0 :(得分:9)
Symfony 3 FYI:命令现在是:
php bin/console debug:router --env=prod
在更新routing.yml后,您还需要使用以下命令清除缓存:
php bin/console cache:clear --env PROD
希望这可以帮助一些人。
答案 1 :(得分:6)
您的配置似乎没问题。我认为这不是问题。 尝试通过以下方式检查应用程序路由:
php app/console router:debug --env=prod
如果结果为空,则应检查是否在:
中定义了任何路径app/config/routing.yml
并将产品路由从routing_dev.yml移至上面列出的配置文件。
祝你好运!
答案 2 :(得分:1)
尝试清理prod缓存,在app / cache / prod中删除所有文件。它适合我。
答案 3 :(得分:1)
在我的情况下,这是在用户public_html目录中安装symfony时出现的“ cache”,“ logs”和“ sessions”目录的文件所有权和权限问题。我用以下命令解决了
$ chmod g+w myproject/var
$ rm –rf myproject/var/cache
$ rm –rf myproject/var/logs
$ rm –rf myproject/var/sessions
$ ls -ld myproject/var
drwxrwx--- 5 whisher www-data 4096 Feb 16 16:35 var/
现在symfony能够创建具有正确权限和所有权的目录。
答案 4 :(得分:-1)
php app / console cache:clear --env = prod