javascript - For an editor like tinyMCE, it is definitely inappropriate for me to directly put its source code into the project for version control. Is there any automation solution?
伊谢尔伦2017-06-21 10:11:17
0
2
818
For an editor like tinyMCE, it is definitely inappropriate for me to directly put its source code into the project for version control. Is there any automation solution?
Thanks for the invitation. First of all, version control isfilesand has little to do with the editor.
Commonly used version control tools are svn and git, and multi-version files are usually stored in svn servers or git servers. The above are divided into private and public servers. But the principle is the same:
Editor edits files and saves them locally.
Submit the file to the server. If overwritten, versions file1, file2, and file3 will be generated
For example, if you use github to store:
New project on github
Clone empty project to local, such as: C: ProjectA
tinyMCE creates a new project and saves the project directory to C:ProjectA
The github client can detect file changes, enter the version title, and the version description can be submitted to github after confirmation
tinyMCE edits any file changes, the github client can detect the changes, and can submit them after confirmation
tinyMCE can be managed through npm and bower, see the instructions for TinyMCE, so you can just putpackage.jsonorbower.jsoninto version control. When using it, first usenpm installorbower installto package the dependencies, and then call the files innode_modulesorbower_components.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Thanks for the invitation.
First of all, version control isfilesand has little to do with the editor.
Commonly used version control tools are svn and git, and multi-version files are usually stored in svn servers or git servers. The above are divided into private and public servers. But the principle is the same:
Editor edits files and saves them locally.
Submit the file to the server. If overwritten, versions file1, file2, and file3 will be generated
For example, if you use github to store:
New project on github
Clone empty project to local, such as: C: ProjectA
tinyMCE creates a new project and saves the project directory to C:ProjectA
The github client can detect file changes, enter the version title, and the version description can be submitted to github after confirmation
tinyMCE edits any file changes, the github client can detect the changes, and can submit them after confirmation
You can view any version of a file on github.
tinyMCE can be managed through npm and bower, see the instructions for TinyMCE, so you can just put
package.jsonorbower.jsoninto version control. When using it, first usenpm installorbower installto package the dependencies, and then call the files innode_modulesorbower_components.