Symfony generating different folder structure than expected
up vote
-1
down vote
favorite
I am reading a book and the author is generating a Symfony project running
composer create-project symfony/symfony mava/
It seems that it install symfony 3.0.1 for him (last stable version).
After he ran this command he says that a structure like below is generated
mava(project root) folders below as subdirectories
app
bin
src
web
vendor
When I run the same command symfony 4 is installed and my folder structure is not even close similar to his, only src and vendor folders are the same. I've already tried to specify the version
composer create-project symfony/symfony mava ^3.0.1
and
composer create-project symfony/symfony mava ^2.0
But I got the same structure, only src and vendor folders.
What is happening?
php symfony
add a comment |
up vote
-1
down vote
favorite
I am reading a book and the author is generating a Symfony project running
composer create-project symfony/symfony mava/
It seems that it install symfony 3.0.1 for him (last stable version).
After he ran this command he says that a structure like below is generated
mava(project root) folders below as subdirectories
app
bin
src
web
vendor
When I run the same command symfony 4 is installed and my folder structure is not even close similar to his, only src and vendor folders are the same. I've already tried to specify the version
composer create-project symfony/symfony mava ^3.0.1
and
composer create-project symfony/symfony mava ^2.0
But I got the same structure, only src and vendor folders.
What is happening?
php symfony
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I am reading a book and the author is generating a Symfony project running
composer create-project symfony/symfony mava/
It seems that it install symfony 3.0.1 for him (last stable version).
After he ran this command he says that a structure like below is generated
mava(project root) folders below as subdirectories
app
bin
src
web
vendor
When I run the same command symfony 4 is installed and my folder structure is not even close similar to his, only src and vendor folders are the same. I've already tried to specify the version
composer create-project symfony/symfony mava ^3.0.1
and
composer create-project symfony/symfony mava ^2.0
But I got the same structure, only src and vendor folders.
What is happening?
php symfony
I am reading a book and the author is generating a Symfony project running
composer create-project symfony/symfony mava/
It seems that it install symfony 3.0.1 for him (last stable version).
After he ran this command he says that a structure like below is generated
mava(project root) folders below as subdirectories
app
bin
src
web
vendor
When I run the same command symfony 4 is installed and my folder structure is not even close similar to his, only src and vendor folders are the same. I've already tried to specify the version
composer create-project symfony/symfony mava ^3.0.1
and
composer create-project symfony/symfony mava ^2.0
But I got the same structure, only src and vendor folders.
What is happening?
php symfony
php symfony
asked Nov 8 at 10:48
Diego Alves
414618
414618
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
You are using the wrong package, for Symfony 3.* it should be symfony/framework-standard-edition
, not symfony/symfony
By using a caret ^
composer will install Symfony 3.4, use tilde instead ~
or a fixed version 3.0.1
Read more about it here: https://getcomposer.org/doc/articles/versions.md#next-significant-release-operators
composer create-project symfony/framework-standard-edition mava 3.0.1
Keep in mind that Symfony 3.0.1 is not maintained anymore.
That's it! I know that Symfony 3.0.1 is not maintained anymore but I follow the book and afterward I will read the docs to see what have changed!
– Diego Alves
Nov 8 at 11:41
1
@DiegoAlves Do yourself a favor and follow a different book. No point in learning Symfony 3 unless you plan to maintain legacy apps. Especially not 3.0 which is basically the same as 2.8.
– Cerad
Nov 8 at 13:11
Did symfony change that much in recent versions? How can a technology that is known to stand out as one of the best implementations of MVC have much to change.., it will be the "internal mechanics"? I am learning Symfony because I am going to implement an e-commerce using Prestashop 1.7.4 and it uses Symfony 3.4.
– Diego Alves
Nov 8 at 15:00
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
You are using the wrong package, for Symfony 3.* it should be symfony/framework-standard-edition
, not symfony/symfony
By using a caret ^
composer will install Symfony 3.4, use tilde instead ~
or a fixed version 3.0.1
Read more about it here: https://getcomposer.org/doc/articles/versions.md#next-significant-release-operators
composer create-project symfony/framework-standard-edition mava 3.0.1
Keep in mind that Symfony 3.0.1 is not maintained anymore.
That's it! I know that Symfony 3.0.1 is not maintained anymore but I follow the book and afterward I will read the docs to see what have changed!
– Diego Alves
Nov 8 at 11:41
1
@DiegoAlves Do yourself a favor and follow a different book. No point in learning Symfony 3 unless you plan to maintain legacy apps. Especially not 3.0 which is basically the same as 2.8.
– Cerad
Nov 8 at 13:11
Did symfony change that much in recent versions? How can a technology that is known to stand out as one of the best implementations of MVC have much to change.., it will be the "internal mechanics"? I am learning Symfony because I am going to implement an e-commerce using Prestashop 1.7.4 and it uses Symfony 3.4.
– Diego Alves
Nov 8 at 15:00
add a comment |
up vote
2
down vote
accepted
You are using the wrong package, for Symfony 3.* it should be symfony/framework-standard-edition
, not symfony/symfony
By using a caret ^
composer will install Symfony 3.4, use tilde instead ~
or a fixed version 3.0.1
Read more about it here: https://getcomposer.org/doc/articles/versions.md#next-significant-release-operators
composer create-project symfony/framework-standard-edition mava 3.0.1
Keep in mind that Symfony 3.0.1 is not maintained anymore.
That's it! I know that Symfony 3.0.1 is not maintained anymore but I follow the book and afterward I will read the docs to see what have changed!
– Diego Alves
Nov 8 at 11:41
1
@DiegoAlves Do yourself a favor and follow a different book. No point in learning Symfony 3 unless you plan to maintain legacy apps. Especially not 3.0 which is basically the same as 2.8.
– Cerad
Nov 8 at 13:11
Did symfony change that much in recent versions? How can a technology that is known to stand out as one of the best implementations of MVC have much to change.., it will be the "internal mechanics"? I am learning Symfony because I am going to implement an e-commerce using Prestashop 1.7.4 and it uses Symfony 3.4.
– Diego Alves
Nov 8 at 15:00
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
You are using the wrong package, for Symfony 3.* it should be symfony/framework-standard-edition
, not symfony/symfony
By using a caret ^
composer will install Symfony 3.4, use tilde instead ~
or a fixed version 3.0.1
Read more about it here: https://getcomposer.org/doc/articles/versions.md#next-significant-release-operators
composer create-project symfony/framework-standard-edition mava 3.0.1
Keep in mind that Symfony 3.0.1 is not maintained anymore.
You are using the wrong package, for Symfony 3.* it should be symfony/framework-standard-edition
, not symfony/symfony
By using a caret ^
composer will install Symfony 3.4, use tilde instead ~
or a fixed version 3.0.1
Read more about it here: https://getcomposer.org/doc/articles/versions.md#next-significant-release-operators
composer create-project symfony/framework-standard-edition mava 3.0.1
Keep in mind that Symfony 3.0.1 is not maintained anymore.
answered Nov 8 at 11:15
Iwan Wijaya
93269
93269
That's it! I know that Symfony 3.0.1 is not maintained anymore but I follow the book and afterward I will read the docs to see what have changed!
– Diego Alves
Nov 8 at 11:41
1
@DiegoAlves Do yourself a favor and follow a different book. No point in learning Symfony 3 unless you plan to maintain legacy apps. Especially not 3.0 which is basically the same as 2.8.
– Cerad
Nov 8 at 13:11
Did symfony change that much in recent versions? How can a technology that is known to stand out as one of the best implementations of MVC have much to change.., it will be the "internal mechanics"? I am learning Symfony because I am going to implement an e-commerce using Prestashop 1.7.4 and it uses Symfony 3.4.
– Diego Alves
Nov 8 at 15:00
add a comment |
That's it! I know that Symfony 3.0.1 is not maintained anymore but I follow the book and afterward I will read the docs to see what have changed!
– Diego Alves
Nov 8 at 11:41
1
@DiegoAlves Do yourself a favor and follow a different book. No point in learning Symfony 3 unless you plan to maintain legacy apps. Especially not 3.0 which is basically the same as 2.8.
– Cerad
Nov 8 at 13:11
Did symfony change that much in recent versions? How can a technology that is known to stand out as one of the best implementations of MVC have much to change.., it will be the "internal mechanics"? I am learning Symfony because I am going to implement an e-commerce using Prestashop 1.7.4 and it uses Symfony 3.4.
– Diego Alves
Nov 8 at 15:00
That's it! I know that Symfony 3.0.1 is not maintained anymore but I follow the book and afterward I will read the docs to see what have changed!
– Diego Alves
Nov 8 at 11:41
That's it! I know that Symfony 3.0.1 is not maintained anymore but I follow the book and afterward I will read the docs to see what have changed!
– Diego Alves
Nov 8 at 11:41
1
1
@DiegoAlves Do yourself a favor and follow a different book. No point in learning Symfony 3 unless you plan to maintain legacy apps. Especially not 3.0 which is basically the same as 2.8.
– Cerad
Nov 8 at 13:11
@DiegoAlves Do yourself a favor and follow a different book. No point in learning Symfony 3 unless you plan to maintain legacy apps. Especially not 3.0 which is basically the same as 2.8.
– Cerad
Nov 8 at 13:11
Did symfony change that much in recent versions? How can a technology that is known to stand out as one of the best implementations of MVC have much to change.., it will be the "internal mechanics"? I am learning Symfony because I am going to implement an e-commerce using Prestashop 1.7.4 and it uses Symfony 3.4.
– Diego Alves
Nov 8 at 15:00
Did symfony change that much in recent versions? How can a technology that is known to stand out as one of the best implementations of MVC have much to change.., it will be the "internal mechanics"? I am learning Symfony because I am going to implement an e-commerce using Prestashop 1.7.4 and it uses Symfony 3.4.
– Diego Alves
Nov 8 at 15:00
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53206149%2fsymfony-generating-different-folder-structure-than-expected%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown