...
- "File Manager" service should have a custom start-up process that differs from a normal stack
- User logs into NDS Labs UI
- User presses "Browse Files", which hits a new "/api/browse" REST endpoint
- API server checks for running file manager
- if no file manager is found, one is started
- User is directed to their running file manager UI
- Is the "File Manager" just a spec?
- There is no reason why this cannot be a spec
- We may want to hide this in the UI, if it would be trivial
- Is the "File Manager" spec hidden in the catalog view?
- Given our "custom start" proposed above, we don't need to show this in the catalog
- That said, there is no harm in showing this in the catalog
- authentication?
- we will look into doing this at the ingress level
- See
Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-308
Cloud Commander
Code Block | ||||
---|---|---|---|---|
| ||||
{
"id": "",
"key": "cloudcmd",
"label": "Cloud Commander",
"description": "Cloud file manager and editor",
"logo": "",
"maintainer": "",
"requiresVolume": false,
"image": {
"registry": "",
"name": "coderaiser/cloudcmd",
"tags": [
"5.5.1-alpine",
"5.5.1",
"latest"
]
},
"display": "stack",
"access": "external",
"depends": [],
"config": [],
"command": null,
"args": [ "--root", "/home/$(NAMESPACE)" ],
"ports": [
{
"port": 8000,
"protocol": "http"
}
],
"repositories": null,
"readinessProbe": {
"type": "",
"path": "",
"port": 0,
"initialDelay": 0,
"timeout": 0
},
"volumeMounts": [],
"resourceLimits": {
"cpuMax": 500,
"cpuDefault": 100,
"memMax": 1000,
"memDefault": 50
},
"catalog": "user",
"developerEnvironment": "",
"tags": [
"21",
"6"
]
} |