-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Cookbook] [Workflow] add a page about getting a symfony2 project followed by Subversion #965
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I know the |
---------------------------- | ||
|
||
The biggest difference between `git`_ and `svn`_ is that Subversion *needs* a | ||
ventral repository to work. You then have several solutions : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quite a nice one though haha
Added modifications based on comments |
.. tip:: | ||
|
||
`git`_ has to be installed to run ``bin/vendors``, this is the protocol | ||
used to fetch vendor libraries. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be mentioned earlier as you already use the script in the previous section.
…t followed in Subversion
New push with git tip early in the code (after first bin/vendors use) |
[Cookbook] [Workflow] add a page about getting a symfony2 project followed by Subversion
Merged! Thanks Stefan - I think there are lots of people wondering about this, especially whether or not you can store symfony in subversion with respect to the vendors (which of course you can). So, thanks for taking this on! |
This page is an adaptation of the git one, I had to do this exercise for a particular reason and thought that it would be helpful to share.
The flaw I see here is that some parts are common to the two pages and could be written in a more generic manner and included in both of them (avoiding future risk of async).
I will dive a bit more in reStructuredText and propose another pull request when this is done.