The major issue with shared hosting in my experience are:
- performance, can be really poor in some cases with no performance
guarantees - you can have a page responding in 1 sec, another time 20
sec and you have no control over this. Also if you are over your quota
in resource usage (cpu mostly) you are being cut off.
- symfony deployment - easier to deploy if someone has ssh access.
In my case I need it because I'm using svn to update project code on
the server.
- can not do advanced configuration for improved performance, be
that Apache, PHP or MySQL, e.g. install opcode cache such as APC, move
rewrite rules to Apache config. All these tweaks can provide a huge
boost (in the order of 3x - 10x ..).
Then again your requirements may be different and you can be more than
happy with shared hosting.
For instance I use shared hosting for personal usage but for business
the company I work for has collocation facilities for its servers.
gabriel
On May 29, 10:46 am, comb <sa...@gmx.net> wrote:
> Hi!
>
> Obiously it takes some tweaks to run symfony 1.4 on a shared host, but
> what's wrong with it?
> One can add a .htaccess files to prevent unauthorized access for the
> hole symfony project folder, another one for the web/-directory to
> enable normal access there and then pointhttp://domain.comto the
> web/-dir.
> Why not?
>
> The only thing I can imagine is that the uploads mostly have to be
> done by hand, but that's ok with me since it'll usually be a small
> project if it runs on a shared host.
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
