Share the project development ideas learned in the last few days

I had a little habit of doing a blog post in January. But seeing the bottom of this month, I feel that the continuity of this time is interrupted by me, not very good.

So I forced to force, to make this article.

Read the premise is that you agree that PHP is the best language (I certainly do not agree, why I agree, haha). It happened the other day. A framework for sharing the front-end separation and development at the same time. I think he solved at least 2 questions.

Front-end separation

We usually use asb.net MVC when it comes to the part of dynamic data that is the most troublesome. First a page, the server to analyze the HTML hierarchy, and then get a general layout (layouts) out. Then it involves the dynamic data output, to use the razor syntax to traverse, to fill .

Filling is not in the way. The problem is that you modify the HTML structure, it is a pleasant feeling, it is possible that the above work from the second step to redo (copy HTML, output data with razor)

And then, our dear colleague proposed to use Laravel this PHP framework. The idea he gave was this. Let the front end learn some basic PHP syntax. Use PHP to cobble together Web pages. The PHP Modular page is involved in the template page and the content page. Then these PHP view files and data format are agreed, then the front-end in the controller to write their own data, fill their own, The front-end is included as a subset of the entire project and does not have to know the specifics of the server's implementation, but he knows what the data looks like. This solves the contradiction between the front and back. Prerequisites:

Page modularity

All say PHP glue, you can quickly merge the various modules together. Just use the server language, this is a very simple thing

Version Iteration Issues

Version iterations sometimes in addition to updates, there should be a rollback. Rollback is the result that everyone wants. I think it is the most effective solution in a short time when there is a serious mistake in some place. Updates to the service-side program not to mention, the front-end words, These static files are related to CS and JS. Static files are easy to cache. But if the browser caches a static resource with a problem, then with a CDN, that's a big problem.

So at this point. With a md5/guid at the end of each file at the time of construction, the static resources requested by each version are different. The problem with the iteration of the version is solved (I did not listen to the specific plan at that time, give a thought to their own brain repair, haha). Use with the version management system

Personal feeling of inadequacy:

1.cdn into a garbage dump (this problem is a pseudo-problem, CDN is calculated traffic, so dump on the dump, haha)

2 because each time the upload is a new static resources, so upload will waste a little more time

Laravel This frame pretty good, many things inside feel and asb.net mvc Common. Like template page, filter (called Middleware in Laravel), packaged request and response ...

Share the project development ideas learned in the last few days