[[appendix_hve_project_json]] === Appendix B: Helix Versioning Engine Project JSON Returns projects that are stored in a single Helix Versioning Engine server. If the `HVE_PROJECT_PATH` setting is specified, this will return all directories under that path as projects. The project `id` is encoded to be a specific part of a URL. It is the application's responsibility to deal with any reconfiguration of the `HVE_PROJECT_PATH` setting. The project `id` is only valid for the same setting. The project `name` is also the name of the directory, just not URL-safe. The `server` property will include the `HVE_PROJECT_PATH` setting as the URL path. The content type of this JSON is `application/vnd.perforce.project.hve.v1+json`. The simple string ID is `hve`. ==== JSON Structure [cols="3*", options="header"] |=== | Property | Required | Description | `depotPath` | Yes | The absolute depot path to the folder on the server. |===
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 15741 | ptomiak | Branch HWS for my use. | ||
//guest/perforce_software/helix-web-services/main/source/doc/appendices/b_hve_project_json.asc | |||||
#1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
//guest/perforce_software/helix-web-services/main/doc/appendices/b_hve_project_json.asc | |||||
#1 | 15437 | tjuricek |
Basic "HVE Project" implementation. This will allow directories in a HVE instance to host 'projects' for use by helix sync. There are no methods defined for creating the projects, however. This does not include any specialization or testing in the Qt API yet. I may investigate creating a "higher level" interface for Qt client apps. |