Ultimately, symfony is totally 100% open. The advice given in the
documentation is (now) a conglomeration of best practices that have
been "discovered" as symfony has matured. Because of symfony's openess
you can change anything you like, but because of symfony's maturity
the documentation points out the things are known to generally work
the best in most situations so you are far better off just sticking to
whats advised.

Also, thats one of the reasons to use symfony ... convention over
configuration. If everything is setup conventionally (as per
documentation) you will do less configuring and spend more time being
productive.

On Sat, Feb 20, 2010 at 10:12 PM, Thierry Boulanger
<[email protected]> wrote:
> Hello Symfonians friends,
> I'm a really really beginner. In the "Pracatical Symfony" is mentionned that
> we have to create these directories /lib/vendor.
> Could we call these directories with other names?
> same questions for sfprojects
>
> mkdir -p lib/vendor
> mkdir -p /home/sfprojects/jobeet
>
> Thanks everyone
>
>
>
> --
> 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.
>



-- 
Gareth McCumskey
http://garethmccumskey.blogspot.com
twitter: @garethmcc

-- 
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.

Reply via email to