[[appendix_config_services]] === Appendix D: Service Configuration JSON ==== JSON Structure A service configuration document is a JSON array of objects. Each object contains the following properties: [cols="2*", options="header"] |=== | Property | Type | Description | `type` | String | The type of service available in the system. One of `p4d`, `git-swarm`, `git-fusion`, `swarm`, or `commons`. | `uri` | Array | Describes connection information to the service. For example, [`p4://perforce.mycompany.com:1699`], or [`https://git-fusion.mycompany.com`, `ssh://git-fusion.mycompany.com`]. |=== ==== Stored Format The service configuration JSON is a file pointed to by the `SERVICE_CONFIGURATION` variable. See <<system_configuration>> for details. It is assumed that the configuration is maintained by the system administrator. Edits to files should be coordinated across all HWS instances.
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #1 | 15688 | Doug Scheirer |
Populate -o //guest/perforce_software/helix-web-services/... //guest/doug_scheirer/helix-web-services/.... |
||
| //guest/perforce_software/helix-web-services/main/source/doc/appendices/d_config_services.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/d_config_services.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. |
||
| //guest/perforce_software/helix-web-services/main/doc/appendices/c_config_services.asc | |||||
| #1 | 15297 | tjuricek |
Implement of 'cluster services' configuration. The configuration will be stored in a local JSON file, which is expected to be maintained by the systems admin. Eventually, it's expected to have this sort of thing implemented via Helix Admin. |
||