Changing description of symfony installation to composer #1993
Conversation
|
IMO, you should link to the composer doc |
|
I also tend to add a link to composer. Of course it distracts the user because he needs to read a bit more, but learning composer is essential in my eyes. And the docs don't need to be changed if composer changes his installation method or anything. On the other hand, adding two more commands (to download and execute composer) would not harm the docs much. But if installation of composer changes, the docs also have to change. So there are pros and cons to this as well. |
| Next, create an ``app/bootstrap.php`` file. Use it to ``require`` the two | ||
| files in the application and to configure the autoloader: | ||
| In your root directory, create a ``composer.json`` file with the following | ||
| content: |
There was a problem hiding this comment.
I don't like this method, the recommend way to start a symfony project is:
$ php composer.phar create-project symfony/framework-standard-edition 2.1.x path/to/project
There was a problem hiding this comment.
I was under the impression that in this part of the docs, only the symfony core is used, not the full-stack framework?
There was a problem hiding this comment.
Yep, that's right - we're actually only need a few specific components, but of course we're not teaching Composer or those finer details, so I like how you've bright in symfony/symfony via Composer.
|
Hi Sebastian! I just left you some comments, but this is really really great - nice work! I'll merge in after the few tweaks. Thanks! |
Changing description of symfony installation to composer
|
Awesome Sebastian! Thanks so much for this, merged - looks really great! |
| @@ -460,7 +462,7 @@ the HTTP response being returned. Use them to improve the blog: | |||
|
|
|||
| <?php | |||
| // index.php | |||
| require_once 'app/bootstrap.php'; | |||
| require_once 'vendor/bootstrap.php'; | |||
There was a problem hiding this comment.
Just starting w/symfony. Right now at this part in the book. Got set with composer as shown. No vendor/bootstrap.php was created, only vendor/autoload.php. I made a bootstrap from https://github.com/ruian/RuianSeoBundle/blob/master/vendor/bootstrap.php
There was a problem hiding this comment.
There was a problem hiding this comment.
Hey, thanks. Your reply means a lot. On first look symfony looks friendly
and powerful but also intimidating and difficult to know how to approach it.
I think I have a feel for what the page at
http://symfony.com/doc/current/book/from_flat_php_to_symfony2.html is
intended for. It's a really good way to explain things - simple and coming
from plain "flat" basic php with no dependant code involved.
On Sat, Jan 19, 2013 at 1:02 AM, Wouter J notifications@github.com wrote:
In book/from_flat_php_to_symfony2.rst:
@@ -460,7 +462,7 @@ the HTTP response being returned. Use them to improve the blog:
<?php // index.php
- require_once 'app/bootstrap.php';
- require_once 'vendor/bootstrap.php';
@rpmsk https://github.com/rpmsk you are right, there is no
vendor/bootstrap.php, we mean vendor/autoload.php here. I submited a fix
for this: #2157 #2157BTW: You shouldn't use the examples here if you are going to use the full
Symfony framework. This article just shows you what the advantages of this
framework are.—
Reply to this email directly or view it on GitHubhttps://github.com//pull/1993/files#r2705072.
As described in #1951, the docs should show how to use composer to install symfony.
I added no link to resources on how to install composer, mostly because the symfony docs are not very clear on how to download/install composer and how it works.
So the question is if there should be a link to composer, a link to How to Install and Use the Symfony2 Components or a complete install description.