Principles: on-line have to look at the process, the process can be completed on! No specifications no standards.
Operation and maintenance should be developed at the same starting line, operation and maintenance and development should not be out of line (common phenomenon exists a small company.) This change is not good
Operation and maintenance is necessary to understand the business. Let developed to do one thing, you can not worry DIY, first ask themselves and each other a few questions, such as:
- Why do this?
- Who asked to do this thing?
- What is the purpose of this is?
- This is done to solve the problem?
More specific point, the development of the production database to make clear why clear, so clear over the fast recovery of data. prepare in advance.
On making a few hours before the line needs some work
Development services to advance the time and tag line on the confirmation order on-line, direct operation and maintenance operations carried out on the iteration jenkins line. (Improve efficiency)
Advance allows developers to sql need to do my hair, you must perform before sql backup, backup, backup, important things to say three times (not just a database, the iterative update other similar operations have backup problems in order to roll back!) And you must check what data, and to prevent sql execution results you expected result a problem.
On-line process, the need to modify or add what operations can be done in advance (at least several hours in advance), if it might affect business use, until the on-line entry into force command execution can be, for example, modify nginx configuration file, front-end project Add Module , the project can advance on-line on jenkins manually pull the latest code, look at the manual packing process in question, especially the front end of the project, the project always ball dropped on the front line during the impact on the efficiency of the line.