Le 04/05/2011 18:48, Matt Robinson a écrit :
I've been playing with the PRs for a while, but now that the beta is
out, I want to start a real project (a rewrite of
http://directors.mapofpower.com/
). Is there a best practice way of doing this, and if so, is it worth
making a cookbook entry for it? Or am I the only one who doesn't know
what I'm doing? :) Here's what I did with the test projects I wrote to
learn the Symfony Standard PRs:
git clone https://github.com/symfony/symfony-standard.git
myproject
cd myproject
git checkout -B myproject
bin/vendors.sh
# Remove demo stuff, init bundles, etc.
The benefit of it is that when it gets updated, I can upgrade by
running:
git pull origin master
bin/vendors.sh
…and then going through the UPGRADE doc and resolving the occasional
conflict where I can learn what's new. Now this works fine for me, but
it feels a bit strange having my project as a branch of the standard
distribution. The other way I can think of is:
wget http://symfony.com/download?v=Symfony_Standard_2.0.0BETA1.tgz
tar zxvf Symfony_Standard_2.0.0BETA1.tgz
mv Symfony myproject
cd myproject
git init
bin/vendors.sh
# remove demo stuff, init bundles, etc
This is more like how I started projects in symfony 1.4 (create a
subversion repository, add symfony 1.4 as an svn:external, run lib/
vendor/symfony/data/bin/symfony generate:project myproject). But if I
do that, how do I upgrade the standard distribution files when beta 2,
RC1, and Symfony 2 final are released? I wouldn't be able to overwrite
the files, and if config files get changed (like the auto_mapping
feature in beta1), then I either miss out or it breaks. Is that what
the UPGRADE file is for?
I think the second method is probably the right way. I guess the
symfony standard files aren't really supposed to change once Symfony2
goes stable (the symfony 1.4 ones never did), so it doesn't matter,
right? Or is there another better method I haven't thought of?
-- Matt
The second method is the right way. The files provided in the app/
folder of the standard distribution are the configuration of your
project so you will have to change them for your project. And then, if
there is a non-BC change in a further beta release, you will need to do
it by hand.
--
Christophe | Stof
--
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
