The road to blog home
I haven't updated my blog for half a month, and I don't want to move after May Day. A few days ago, the blog moved to the soft cloud, but it was not long ago that the soft cloud had problems, and it was evacuated urgently. Fortunately, the data can be backed up (but when I moved, I set up an automatic backup to the cloud in the early morning every day, just for fear of any problems, the results will come from nothing).
On the second day, we moved the data over quickly, switched the domain name directly, and returned to the original fence host. Anyway, the host still needs to be kept. There is an exit at a critical moment.
From last year to the beginning of this year, I always wanted to buy a cloudcone machine, but I didn't have the 1C2G machine I wanted, so I simply didn't buy it.
Picture upload and cloud shooting
The old tune is repeated. Previously, the configuration of the background ueditor was directly uploaded to the cloud and then photographed. After moving to the soft cloud, it can't be used, nor can it be fixed. So we built a LightPicture , but when the soft cloud machine goes wrong, the program disappears. Although there is no loss, the virtual host cannot use the program.
Find a suitable local direct upload program, which can be implemented on the pure front end. The program is found on github, and its name is: web upload upload
After getting the program, I slightly changed the upload path and naming rules to basically meet my needs.
Before, I thought about putting it on the host, but later I thought it was unsafe. After all, there was no verification, and anyone could upload it directly, so I opened the local browser.
Toss subsite -- knowledge base
In fact, it is just a site that is full of troubles-- knowledge base A long time ago, I used the encyclopedia program, and then switched to the Typecho program, which is equivalent to two Typecho programs. A few days ago, I changed a new theme, and the theme also had some bugs, so I started to change it.
I also changed the feed of reading the knowledge base in the blog sidebar. Now I should not kill myself. Instead, I read files and cache them for one day.
After two days of testing, no problems have been found so far, so use it first.