thinkphp, why does this kind of deployment

Below is a peer-to source, see its deployment does not seem to follow the conventional, I do not know what is the purpose of the whole?

Reply to discussion (solution)

This is only an application developed using thinkphp, and does not necessarily follow the thinkphp directory layout rules
Besides, he just put a level on some of the catalogues.

This is only an application developed using thinkphp, and does not necessarily follow the thinkphp directory layout rules
Besides, he just put a level on some of the catalogues.

So the question is, that it does not follow the general directory deployment method of thinkphp, what is the idea of his deployment?

He is not really good, app,webconfig, those are best not put in the domain can access the path.

He was trying to make the URL shorter.
Another possibility is that the system was originally present, with thinkphp rewriting the control logic
In fact, the downgrade of thinkphp to a plug-in, this practice is very common

The practice of forcing the site into his subdirectory, like Laravel and speedphp, is undesirable, very overbearing
They are convenient, but inconvenience to the deployment of the user

So the question is, that it does not follow the general directory deployment method of thinkphp, what is the idea of his deployment?

3 Floor said to be placed in the deep, 4 floor said in the deep bad, in the end which is good, I am a little dizzy feeling

Dizzy is right, there is no fixed pattern.

Fits, hard to set a pattern, is absolutely not to take

