Yii2 project installation

Yii 2.0 Installation and Setup
1

Hey all.

I am 99% new to Yii2 so I need some basic understanding of best practice. The 1% is that I installed the basic template and got it up and running. I even tried the migration. :)

I am an experienced developer and so I am not new to frameworks, mvc, extensions and all that. I am a pro developer for i.e. TYPO3 and Drupal. Enough of my background. Just so you know I do not need to have it from the beginning.

I got a new job and after a short time, I finally convinced the other developers that the homemade framework was old and not fleksible, not maintainable etc. We are wasting increadible amount of time to maintain existing codebase. And it is getting harder and harder to maintain it.

SO - I am trying to find out how to proove that Yii2 is the way to go. And I need your help for that. I need to build an administration-system from the scratch up. And Yii2 fits perfectly in here, in my oppinion.

I have searched for best practice of how to make "something" and to have an installation-routine for the project. But up to now, it has been unclear for me. I do not want to invent something where others already been.

Does anyone know whats the best practices of installing a project, how to build an installation-program of some sort. I guess you guys do not install i.e. a yii2 based cms by running migrations?

2

That is a difficult question :)

I would probably develop an administration module and then create a Composer project.

Installation would then just be a simple call


composer create-project you/your_starter_project

The basic project template has some initialization code that runs in the post create hook - take a look at the composer.json for that.

As for the actual user-driven installation, one way of doing this is to have either an installation controller or an installation module combined with a check for the existence of a .lock file somewhere…

I haven’t actually looked into creating installers for Yii 2 yet…

I’d advice you to check out a wide range of Yii 2 extensions and browse their code because it will (hopefully) give you many ideas about what makes Yii 2 tick.

This is a good place to look for those:

Yii framework extensions & cms catalog - YiiGist

3

Thanks for the reply. I was thinking the same thing + one more thing. I was thinking of calling the migration-part directly from the controller to install the basic system. And so on.

I am already diving into the world of components, to see if I can develop something to help me here. And I am also looking at various projects of how they are doing it.

I still have some documentation to read because I do not understand fully how Yii2 handles namespaces in modules etc.

Thanks for the links and the info. You pointed me in the right direction. :)

4

Namespaces for modules:


namespace app\modules\yourmodule;

becomes


namespace yourname\yourmodule;

when it is packaged as a Composer package with type ‘yii2-extension’.

For example:


{

	"name": "yourname/yii2-yourmodule-module",

	"description": "description here",

	"type": "yii2-extension",

	"keywords": ["yii2","extension"],

	"license": "LICENSE",

	"authors": [

    	{

        	"name": "author name",

        	"email": "author_email"

    	}

	],

	"require": {

    	"yiisoft/yii2": "*"

	},

	"autoload": {

    	"psr-4": {

        	"yourname\\yourmodule\\": ""

    	}

	}

}
5

So you are suggesting to develop the core system as a seperate new composer package, instead of keeping it "in the project"?

I can see the benefits here but what would you then suggest to handle the modules for the project?

Before you can answer that, I need to tell the aim of the project. It is mainly going to be an administration-system. Up to now the "client" has everything in one big system, special developed. And there is so many "coding standards" in it, so you go blind. I want to change all that so I can help me and the other developers to focus more on the functionality instead of the code.

One of the directions is to have a core system, and install it multiple times with special developed modules in each system. Some of the modules will be in installation no. 1 and others in installation no. 2

It is almost like a cms system like Joomla with enabling/disabling of things.

I am really grateful of your input. It is a big help. I am very keen about the architecture and wants the best. :)

6

By having the modules as extensions you can version them, etc.

(Think sub-modules (or whatever they are called) in Git)

But for starters, it would probably be easier to just implement the modules first, and then worry about turning them into extensions (or not) later. :)

7

Oh I definately love YiiGist. I did not know that existed. Thanks for that vault of gold. :)

About the extensions, I love that way of thinking for modules. That means that the modules can have their own history. Love it.

The other developers did not know of composer either. So I have my work cut out… :)

Btw, I do know about git submodules. If you ever need to go that way, turn away and run. Just run :D

8

So from a pro developers point of view, the right aproach (simplified a lot) will be to have the base almost untouched, with only the SiteController to start it all up and activate the first module. And then let all the magic happens in various modules?

9

I am not a pro developer, but - from what I’ve seen, using modules is one way to go :)

You can then split the responsibilities between you in a nice way.

It’s not going to work for all applications, though.

I would not use modules if there is no clear separation between the components of the application.

((And luckily, I haven’t touched Git submodules so far. :P ))

10

Thank you. You have been a great help. :) Maybe there will be new questions, but I feel “suited up” to start developing.

11

So, I just stumbled upon Deployer which has support for Yii 2: http://deployer.org/

It is distributed as a phar and seems like a very capable tool :)

That could be an alternative to using a Composer project - I am definitely going to test drive it myself!

12

Hi CoRex and Jacmoe. Am also very new, still a baby developer. Have a little above 1 year experience with PHP development. Have never used a framework before besides wordpress and joomla. All other projects are hand coded. I know frameworks are a way to go.

My questions are:

  1. What is/are the dangers/demerits of installing Yii (or any other framework) via their archive files? Must I install via composer?

  2. Must I use stuff like codeception for testing?

I have been studying a book I got from packt on web development using Yii2 and it’s getting too complex and errors are erupting here and there.

I would appreciate all the help I can get.

13

The errors erupting all over the place will eventually - if you stick it out - cease and you will learn the ropes :)

Yes, you definitely need to be using Composer. Because it not only installs Yii but the dependencies as well. And you will need Composer to install Yii extensions.

While you theoretically can install everything manually, you will miss out on version control and easy upgrade/downgrade.

Learn to love Composer - it is in my opinion one of the most important changes from Yii 1 that has made Yii 2 so much better!

No, you don’t need to be using Codeception, but since it is built-in it would be less wise to use something else. Especially when Codeception is easy compared to ‘the competition’.

The sooner you get to know the framework, the better.

Feel free to open up topics in the Yii 2 general discussion forum when the errors erupt. ;)

14

Thanks a lot. I have decided to face it and get going. I would stick to your advice. :D

15

Hi royacle.

A little word from me. I agree in all what jacmoe writes. Even the bigger CMS’es are going composer. TYPO3 is fully supporting composer. Dont know status of Drupal, Joomla is on its way. Dont know about WordPress. So you can see, if the big ones see’s the light, so can we :D

After my brief time to Yii2 I found that Yii2 is a very solid framework with a lot of supporters. It is of course important to use a solid framework, but even more important are the developers behind it and all the contributors. These are your buddies. I have developed my own framework from scratch up some years ago. I would not do that again. I would rather take a framework i.e. Yii2 and base my development on that.

That said, Yii2 cannot handle everything, but bear in mind that it is "only" a framework. I had to develop some widgets from my own because I found Yii2 was missing what I needed. But in doing that, I did not start from scratch, since the foundation (Yii2) was there.

Since you call yourself a baby developer, I will give some advice’s to you. If you do not agree, trash them, but I am pretty sure that these will help you grow as developer. There are a lot of developers, but if you want to be a top developer, read these advice’s. :) There have been written large books on these subjects, but here is a few basic ones.

I could write much more about these advices, but these will help you get started. And yes, Yii2 is a VERY good choice in growing as developer.

/CoRex