Here are three ways to share repository folders. Wagby recommends "version control system usage method".
The design information (repository) edited by WagbyDesigner is managed in a folder called "repository" located right under the folder where Wagby is installed.For details of this folder structure, see "Repository> Repository compositionPlease read.
In team development, you need to share this repository folder.
WagbyDesigner is a web application.Therefore, multiple developers log on to one WagbyDesigner (running on the server) at the same time and rewrite the design information with everyone.
You can use a well-known version control system to share Wagby's repository.There are cvs, subversion, Git, etc. as prominent products.Both are provided as open source software and can be used free of charge.
Regardless of which product you use, you can share Wagby's repository.
The subjects managed by the version control system may also be referred to as "repositories".
Since Wagby's "repository" is design information, it has two meanings with the same word, but explains it separately so as not to be confused.
Recording changes in the version control system is called "commit".
The version control system manages the state on a commit basis.Moreover, it has a mechanism that can return to the information at that time at any time.
The version control system has a mechanism to check the editing history.The figure shows an example of confirming the editing history using SourceTree, a free version control software provided by Atlassian.
It is possible to restore the original state while checking the contents of the past files.
When multiple developers edit the same model, each modification may collide.This is called a conflict.
In this case, the developer checks visually and decides which editing to activate (leaves) and decides to commit.
In addition to the design information (repository folder), when customizing, add the customize folder to the version management system management target.
Automatically generated code is not subject to version control.This is because it can always be generated automatically.
Other models other than models changed by developers may be changed.This happens when you perform operations related to menus.
For details, refer to "Repository> Repository Structure and Team Development> Menu> Points to note when developing a teamPlease read.
Configuration files such as $ (DEVHOME) /. Project etc are not managed by the version control system.This is because the files below work / srcgen / eclipse are overwritten to $ (DEVHOME) at build time.
On the other hand, $ (DEVHOME) / customize / eclipse /, which is a folder for storing customized eclipse configuration files, overrides work / srcgen / eclipse.When preparing this folder, please use it as a target of version control system.