SOAJS helps you orchestrating different types pf repositories, here is the soa.json for a repository with static content aka react, angular, etc ...
soa.json for type=static
{
"name": "frontend",
"type": "static",
"group": "Examples",
"description": "This is the description of your static",
"tags": ["tag1", "tag2"],
"subType": "frontend",
"attributes": {
"att1": ["att1.1", "att1.2"],
"att2": ["att2.1", "att2.2"]
},
"tab": {
"main": "Main tab",
"sub": "Sub tab"
},
"program": ["soajs"],
"documentation": {
"readme": "/doc/markupfile",
"release": "/doc/markupfile"
},
"version": "1",
"profile": {
//free to add whatever you want
}
}
| Variable | Required | description | example | default |
|---|---|---|---|---|
| UI meta data | ||||
| type | Yes | The following type is supported: static, service, daemon, multi, config, custom (anything else) | if not set the default type will be custom. | custom |
| tab | No | - | - | |
| subType | No | frontend | ||
| name | Yes | The name of the static content. It has to be unique and not been used by other static contents at the Frontend catalog. | ||
| description | No | The static description to appear in the Frontend catalog UI | "This is a string" | - |
| Search meta data | ||||
| tags | No | - | ||
| attributes | No | - | ||
| program | No | - | ||
| Documentation meta data | ||||
| documentation | No | - | ||
| Type meta data | ||||
| version | Yes | The version of the static content. make sure it has the following syntax: a string of /[0-9]+(.[0-9]+)?/ | "1" or "1.1" | "1" |
0 Comments