Why the official website download WordPress directly deployed to Gae and SAE can not use?

The direct reason that SAE cannot install native WordPress is that it does not support writing. Because writing is not supported, the configuration file at the time of installation cannot be created, and the Run-time template and data cache file cannot be generated. Other common applications don't run for a similar reason: simple operations like editing templates don't work on the SAE, because templates are usually saved as files, and templates cannot be saved when edited. With the popular Smarty template engine as an example, the rendering template will first check that there is no template cache, if not created first, this also requires writing file permissions. Features such as one-click Upgrades, app stores, and template stores built into common software are also paralyzed by the inability to create files.

If you want to transplant the native program to the SAE, need to do a lot of functional deletions, temporary file classes (file caching) requirements, SAE provides a wrappers package, can be modified code support, but for the need to persist the storage of the program class file requirements even if the change code can not support, such as the application store, template store, One-click Upgrade, a key to play patches and other functions are not good. Built-in stores this feature is an important profit channel for application developers, and does not support these features and developers are less interested in developing SAE platform versions. Anyway, I myself once ambitious want to be compatible SAE platform, later found everywhere limited, solve problems will increase costs, but bring no revenue, decisively give up.

=======================================================

The disadvantage of not supporting writing is finished, here is an official gift for SAE:

I guess I'm a layman. Technical reasons for writing are not supported, possibly because distributed systems face some challenges in file synchronization, consistency, and performance if they are to support writing.

But the root cause is that product managers don't pay enough attention to the seriousness of the problem: there are technical problems but they are not impossible to solve. If I am the SAE Product Manager, I must support file writing, this is not compromise! But in other respects can make some concessions, such as: Write can be slow, it does not matter, consistency in a very short period of time can not guarantee that there is no relationship, the written method is limited also does not matter.

I think so:

Like SAE, an Internet base service provider, like a power plant, he invented a new current-transmission technology with a lot of advantages in terms of price. The only disadvantage is that the household voltage is 1000V (for example), resulting in the user all the existing electrical appliances can not be used directly, if necessary, the need for electrical support 1000V input voltage. Have the strength of the factory, you can specialize in the transformation of equipment to make compatible access, generally ordinary users do not have such a large capacity, can only hope that the electrical manufacturers to produce 1000V version of the electrical appliances. And Haier, Changhong? Do not want to specialize in this version, because each model is more than one version, in warehousing, logistics, marketing, research and development, aftermarket, accessories have brought additional costs, but 1000V users are very few, even if the development will not bring too high additional benefits. So, there has been no heavyweight support from manufacturers. Occasionally some small factories released the 1000V version, but users worry that once the power plant closed, a room of 1000V electrical appliances into scrap iron, so sales are also very bleak, followed by less manufacturers are willing to produce 1000V version.

The threshold is high so the user is few, the user is less so the manufacturer is few, the manufacturer is less so the user is less, a perfect dead cycle.

Above my fictitious 1000V power plant faces the predicament is the SAE the present situation, Word: applauded not to draw.

To solve the power plant dilemma is simple, in short: compatible! In the household, give the user a smart transformer, converter, pai. So the user's original TV, computer, refrigerator and so on without the need for additional modification can access. If there is a new 1000V-supported appliance in the future, it can be compatible with a dedicated cartridge. This reduces the cost of user Switching, and overnight all households become potential users of 1000V electricity.

To solve the SAE dilemma is also very simple: also compatible! As long as one is compatible, the number of potential users is a few more orders of magnitude. Otherwise, let your SAE merit more, cannot use, equal to zero. Incompatibility has two fatal problems:

1 General software can not be directly used: Castration version in the function, upgrade have congenital defects, unbearable. To use the SAE almost only to develop themselves. This article will not be able to develop a lot of small teams, individual entrepreneurs outside the door.

2 User platform Risk: If the startup team chooses SAE as a service provider, it means a lot of risk. If the SAE has made a mistake on the content audit, it is possible that the entire business has been stopped (this is not alarmist, Sina Read has been stopped), and some entrepreneurial team by the SAE active envelope. Either way, if something happens because the system is not compatible (deep reliance on SAE services), even if you buy other IDC services, the system is still unable to run. Only the SAE recovery, or the emergency system to the normal server architecture.

So, how compatible?

File writing as an example, is simply sacrificing some performance to do synchronization work, is completely achievable. Consider that most programs are read and write less, sacrificing a bit of performance at the time of writing, with minimal impact on the overall performance of the program.

And then take MySQL as an example, the SAE's MySQL connection does not need what user name and so on, directly a new Saemysql (); However, in order to be compatible you can still accept incoming parameters, but regardless of what is passed in the current instance of the fixed account to complete the database connection, and normal PHP, like MySQL.

In addition, the SAE enforces the SVN deployment code I guess it's also based on consistency, and you can add an FTP approach based on the way you keep SVN.

The prescription comes out, the concrete implementation is the technical question, the Sina cow person a lot of, the technical question has the solution forever. The ultimate goal is to:

The vast majority of sites, as long as the webmaster willing, can be a line of code not to change the smooth migration to the SAE platform; When you want to swap with other platforms, but also painless smooth move out, no worries.

I am on the surface is SAE black, actually is true love, I said finished.