I think ServerGrove is an excellent choice when it comes to Symfony. 80% of their very helpful blog posts are also about Symfony. These guys use Symfony and know it very well.
Like Colum, I think the hosting company doesn't really matters.
However for Symfony I would recommend a dedicated hosting since you may need to change PHP and Apache configuration (since Symfony 1.x uses a .htaccess, and sometimes you need to make aliases to something like .../sf/data and .../sf/web directories to be able to use some Javascript and CSS code from Symfony)
When looking for a server, there is no "best" host. Each one has its own differences. I personally would recommend Dreamhost, because it is wildly used and has some great features. Other people would disagree, because mostly it is a matter of preference.
Most shared hosts allow you to put a php.ini in your home directory, and that can serve for your php.ini.
Kenneth, my company runs a Symfony 1.1 dev server on a shared hosting solution. It mostly just depends on what the host is willing to give you. There isn't a specific need for a dedicated solution, though our production servers ARE dedicated primarily because my company sends thousands of emails daily and it was the only option the host would allow with that scenario. When money is tight and you're first getting started, I'd personally start small and work up.
A word of warning--Symfony is by far the most bloated framework that I've ever seen. It takes 15 different steps on my company's site to render a page, and that results in crazy processing and delivery times for pages. So for starters a shared solution may work for you, but as you add users, it will likely bog down quite a bit. We're so unhappy with Symfony that after our latest release my team was deployed to re-write our solution to get rid of Symofony. Fun times!
发布评论
评论（4）
我认为 ServerGrove 是 Symfony 的绝佳选择。他们 80% 非常有用的博客文章也是关于 Symfony 的。这些人使用 Symfony 并且非常了解它。
I think ServerGrove is an excellent choice when it comes to Symfony. 80% of their very helpful blog posts are also about Symfony. These guys use Symfony and know it very well.
和 Colum 一样，我认为托管公司并不重要。
然而，对于 Symfony，我建议使用专用托管，因为您可能需要更改 PHP 和 Apache 配置（因为 Symfony 1.x 使用 .htaccess，有时您需要为 .../sf/data 和 .. ./sf/web 目录，以便能够使用 Symfony 中的一些 Javascript 和 CSS 代码）
此页面也可能会有所帮助：http://trac.symfony-project.org/wiki/HostsSupportingSymfony
Like Colum, I think the hosting company doesn't really matters.
However for Symfony I would recommend a dedicated hosting since you may need to change PHP and Apache configuration (since Symfony 1.x uses a .htaccess, and sometimes you need to make aliases to something like .../sf/data and .../sf/web directories to be able to use some Javascript and CSS code from Symfony)
This page may be as well be helpful : http://trac.symfony-project.org/wiki/HostsSupportingSymfony
在寻找服务器时，不存在“最佳”主机。每一种都有其自身的差异。我个人会推荐 Dreamhost，因为它被广泛使用并且有一些很棒的功能。其他人可能会不同意，因为这主要是一个偏好问题。
大多数共享主机允许您将 php.ini 放在您的主目录中，这可以为您的 php.ini 服务。
When looking for a server, there is no "best" host. Each one has its own differences. I personally would recommend Dreamhost, because it is wildly used and has some great features. Other people would disagree, because mostly it is a matter of preference.
Most shared hosts allow you to put a php.ini in your home directory, and that can serve for your php.ini.
Kenneth，我的公司在共享托管解决方案上运行 Symfony 1.1 开发服务器。这主要取决于主人愿意给你什么。尽管我们的生产服务器是专用的，但并不特别需要专用的解决方案，主要是因为我的公司每天发送数千封电子邮件，并且这是主机在这种情况下允许的唯一选择。当资金紧张并且刚开始时，我个人会从小事做起，然后逐步开展。
警告一句——Symfony 是迄今为止我见过的最臃肿的框架。在我公司的网站上，渲染一个页面需要 15 个不同的步骤，这会导致页面的处理和交付时间过长。因此，对于初学者来说，共享解决方案可能适合您，但当您添加用户时，它可能会陷入相当大的困境。我们对 Symfony 非常不满意，以至于在最新版本发布后，我的团队被部署重写我们的解决方案以摆脱 Symfony。欢乐时光！
Kenneth, my company runs a Symfony 1.1 dev server on a shared hosting solution. It mostly just depends on what the host is willing to give you. There isn't a specific need for a dedicated solution, though our production servers ARE dedicated primarily because my company sends thousands of emails daily and it was the only option the host would allow with that scenario. When money is tight and you're first getting started, I'd personally start small and work up.
A word of warning--Symfony is by far the most bloated framework that I've ever seen. It takes 15 different steps on my company's site to render a page, and that results in crazy processing and delivery times for pages. So for starters a shared solution may work for you, but as you add users, it will likely bog down quite a bit. We're so unhappy with Symfony that after our latest release my team was deployed to re-write our solution to get rid of Symofony. Fun times!