The nodejs server accesses the txt file in the root directory.
Inaccessible.
I always thought it was caused by the reverse proxy of the nodejs server.
Today I found out that it is not.
It's caused by the configuration of the nginx server.
made some changes
location ~ .*.(js|css|txt)?$ # Just add |txt here.
{
expires 12h;
error_log off;
access_log /dev/null;
}
Continue to iterate on the views engine.
After this iteration, the views engine has completely become a microkernel architecture. The architecture of form engine and block engine is the same.
Do more creative things and less labor-intensive things.
Routes, results, models, methods.
Respect things and respect people.
You must be serious in everything you do.
We must also be serious about things and people.
There are many smart people in this world, but there are no fools. If we have to say there are, there are only two types. One is thinking that you are smart, and the other is always thinking that others are fools.
The form engine has been iterated in the past week. Added address selector. Not very satisfied, let’s do this first and talk about it later. The form title implements conditional configuration and does not have to be limited to a fixed value.
OMS has also made some iterations. Added an order type (free). Modified the order model.
The product management system has also made some iterations, adding a product type and a taxonomy for order classification.
I have always felt that there is something wrong with my form engine, but I have never found it.
It wasn't until yesterday that I discovered that the form items configured using my form engine could not be linked to each other.
It was iterated today to solve this problem and allow linkage between form items.
When the data of a certain form item changes due to user operation, the data or view of the associated form item will change accordingly.
Record a PHP error: the interface return is null, print_r or echo can output, but with a null string at the end.
There are two situations.
1. There is an error in the json string, causing an error in json_decode.
2. There is no return result in the function of the interface, but the result is returned in other functions called.
