On Jun 6, 9:21 am, Ragnis <[email protected]> wrote: > I can't learn it if I can't get it to work. > > Theese "framework guys" never think about those who are using shared > hosting.
The way restrictive shared hosts set up their environments causes problems for any kind of decent sized web application, not to mention the security holes they expose. Most shared hosts are only really suitable for personal home pages and small sites. There are exceptions though, look around and you'll find some that are very framework friendly. Anyway, assuming you are allowed to symlink - why not put your entire site in private_html and symlink public_html to your /web folder? Symfony 2 is being designed with this kind of flexibility in mind, but symfony 1.x was really intended to be a "full stack" framework, which meant drop it in and use it with minimum fuss. > On Jun 5, 9:58 pm, Eno <[email protected]> wrote: > > > On Fri, 4 Jun 2010, Ragnis wrote: > > > Why does it even have to be so complicated.. > > > Actually its not, symfony is quite flexible but it *does* require you read > > and learn the framework to use it well. > > > -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
