It’s a pity.
Then I will deal with the fact that there is.
It’s a pity.
Then I will deal with the fact that there is.
Hello, I have been following and reviewing the development of yii3, and the truth is that now it is difficult to install the yii-project-template application in this way, when @hiqsol started, with a basic web skeleton and a common directory master skeleton. It was super simple, since it allowed the update of the base web skeleton; also the configuration per excellent idea module, now the resources must be installed using wikimedia/composer-merge-plugin, when previously they were simply installed in composer.json with https://active-packagist.org/, for anyone working in yii2 what think twice to migrate to yii3.
Sorry my bad english,
@vanhelvzla thanks for feedback. The decision isn’t final and we want installation to be simple, please post to Basic template vs new Yii 3.0 template as well.
Steps for the Yii2 Web Application installation:
php composer.phar create-project --prefer-dist --stability=dev yiisoft/yii2-app-basic basic
Steps for the Yii3 Web Application installation:
composer create-project --prefer-dist --stability=dev yiisoft/yii-project-template myapp
cd myapp
composer require yiisoft/yii-base-cli
composer require wikimedia/composer-merge-plugin
composer config repositories.ap '{"type": "composer", "url": "https://asset-packagist.org"}'
composer config extra.merge-plugin.include "vendor/*/*/composer.assets.json"
composer require foxy/foxy:^1.0.0
composer require yiisoft/yii-base-web
composer require yiisoft/rbac
The problem is not the number of steps, if it is understood because they are needed, that is why it is easier to mount the complete web application, which already had @hiqsol.
I’m not sure if I’m doing something wrong but I have the assets duplicated:
Directory:
/public_html/node_modules ---> Assets Duplicate (bootstrap, jquery, popper)
/vendor/bower-asset ---> Assets Duplicate (bootstrap)
/vendor/npm-asset ---> Assets Duplicate (jquery, popper)
Does this work for you?
First of all, you either need
composer require wikimedia/composer-merge-plugin
composer config repositories.ap '{"type": "composer", "url": "https://asset-packagist.org"}'
composer config extra.merge-plugin.include "vendor/*/*/composer.assets.json"
or
composer require foxy/foxy:^1.0.0
and also only if you plan to create a web-application, installing both might also be the root-cause of duplicated assets. There’s still some work to do regarding asset handling in the extensions (eg. bower vs. npm and asset-packagist vs. native npm)
Adding no application-base was a design decision taken from here: https://github.com/yiisoft/yii-base-api/issues/1
You also do not need yii-base-cli and yiisoft/rbac, I think. So the web application installation should boil down to
composer create-project --prefer-dist --stability=dev yiisoft/yii-project-template myapp
cd myapp
composer require foxy/foxy:^1.0.0
composer require yiisoft/yii-base-web
Also said in my previous post, not everyone wants to install a web application, see https://github.com/yiisoft/yii-base-api/issues/1 - for example when thinking about a possible combination of Yii 3 as API + a VueJS app.
The goal of a template should be minimum code and maximum flexibility.
But there could be a full-fledged project template having “everything” pre-installed. But this statement is problematic, what and how should it be installed?
I.e. I’ll always use npm for future projects, but it was also a requirement that there’s a PHP only solution.
If people want an easy installation I’d suggest to create an example project based on the template.
I understand it perfectly, but it’s already a decision of @yiiteam, for me what I like about yii is that it’s different from Laravel and the symphony, its ease, its quick line of learning, how easy it is to develop a system, install the template and use gii that is the powerful thing, the new programming frameworks are focused on that path, and I think that sometimes here we go the other way.
What would you change? Install the web-base? With which asset system then?
While I don’t think the current setup process is final, I like that’s it is truly modular, flexible and scriptable.
We could also add some application init commands to yii-console, but these would be just for convenience.
Good day, particularly I think there should be a template to start web applications quickly since the design @hiqsol is already done, and I think it’s excellent because we can update the template without reinstalling something we can not do in yii2 it’s a great progress for all, on the other hand, you can have another template clean of zero so that the most experienced can add the packages of your choice, remember yii "It is fast, safe and efficient and works immediately and preconfigured with reasonable predetermined values. It’s easy to adjust to suit your needs, because Yii has been designed to be flexible. " We can not lose the objective framework.
I don’t agree that a web-application and asset-packagist is a reasonable predetermined value, especially based on the discussions linked above.
The current project template is especially designed to be flexible, but yeah it requires one or two more step in its setup.
@samdark Can/should we create a repo web-project-example or similar which is based on (or uses) yii-project-template and installs a yii-web-base with asset-packagist by default?
Also related: https://github.com/yiisoft/yii-console/issues/12
Just to note that here 
I never use the Web UI, only the console, since the Web UI is so much limited when it comes to extending gii ie. with batch processing.
My bad!
How do you use Gii console with batches? Any example/use case?
Well noted
btw: About application setup … this is how Symfony does it https://symfony.com/doc/current/setup/flex.html - just for reference(!)
We’ve discussed the matter with @schmunk and @cebe and decided that we can have both easy start and a good further flexibility. For that we can strip web application from any JS or CSS dependencies. That would eliminate the need to set up asset systems right away making installation one-liner again.
Simple template will be more than enough to play with and build simple things. If that’s not enough we’ll provide a guide on how to initialize different asset systems.
Perfect, yii2 will be very different from yii3, worries how many extensions will not migrate to yii3.
Hello
imagine that I am a person who does not know anything about Yii and who is knowing the framework for the first time
What steps should I follow to install Yi3?
Follow the steps commented by @vanhelvzla but it does not work
I want a guide for dummy