Online deployment 2

Currently, the project has been officially deployed, launched, and promoted. In addition, it has been deployed more than 20 times, several times for new function deployment, several times for temporary bug fixing, and several times for experience improvement.

Several times are used to copy the entire folder before the new things are deployed, and several times are used to rename the file to be overwritten, adding the current date or even the time before.

After several deployments, I felt that manual copying and backup were a nightmare. Because it was online, not my own data center, there was no leased line, and the bandwidth was not enough, the speed was very slow. More and more people feel how important it is to use scripts to speed up deployment. Whether it is to back up existing code or back up existing databases, you can also add dates to provide materials for future version planning. If it is an interface operation, it will definitely wait for the dead.

Currently, no version definition method is determined. However, the current deployment leaves space for future version planning. The current new function deployment will completely back up the existing programs and databases. The local improvements to bug fixes and experience will add a current date before the existing file. The complete backup can actually be a new version. The version number of the backup is several times, and the previous single file backup with a date is a minor version number. In this way, you can use the backup file to restore the fault generated in the absence of version planning after you define the version later.

At the same time of deployment, write some documents, make some records, time, new functions, bug fixes, and experience improvements. It would be better to cut down some images.

Back up and deploy the bat file on a windows system.

To give full play to the power of batch processing, let's first come to several conventions. The folder location and folder Name of the internal deployment and online deployment are unified, So that you only need to write a set of backup scripts to run them everywhere. Of course, you can also accept user input and decide the folder to be backed up and the physical directory to be backed up. However, we feel that unification will bring great convenience to backup deployment, at least for the time being, and we will continue to improve it in the future based on the scenario.

Now we have made some backup deployment plans. At present, we need to back up IIS folders, SQL Server databases, apache configuration files, tomcat webapps directories, and tomcat configuration files. The deployment is simple. modify the configuration file to overwrite the IIS folder, tomcat folder, update the database structure, and import basic data.

Forbidden. bak.

Full backup is to copy files and databases to the backup directory of disk D, which is differentiated by date + time.

Backup plan:

1. Stop the IIS service and back up the IIS folder.

2. Stop the Database Service and back up the database.

3. Back up the apache configuration file.

4. Back up the tomcat configuration file.

5. Back up the webapps directory of tomcat.

The script can be written as above.

Deployment Plan:

1. Overwrite or add the IIS folder.

2. Change the database structure and import basic data.

3. Modify the apache configuration file.

4. Modify the tomcat configuration file.

5. Overwrite or add the tomcat folder.

The current Alexa ranking of websites.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/11391Ub4-0.png "title =" 201306112319.png"/>

This article is from the "breakthrough IT architects" blog, please be sure to keep this source http://virusswb.blog.51cto.com/115214/1220915