Repository navigation
cannot manage running services with bin/ocis run|ps|kill #77
Description
✗ bin/ocis ps
2020-01-06T14:52:14+01:00 INF Continue without config service=ocis
2020-01-06T14:52:14+01:00 FTL {"id":"go.micro.client","code":500,"detail":"service go.micro.runtime: not found","status":"Internal Server Error"} service=ocis
✗ bin/ocis kill service --name com.owncloud.phoenix
2020-01-06T14:54:41+01:00 INF Continue without config service=ocis
2020-01-06T14:54:41+01:00 FTL {"id":"go.micro.client","code":500,"detail":"service go.micro.runtime: not found","status":"Internal Server Error"} service=ocis
Activity
[-]cannot list running services with `bin/ocis ps`[/-][+]cannot manage running services with `bin/ocis ps|kill`[/+]PVince81 commentedon Mar 19, 2020
The help is confusing, it looks like one must run
ocis run service_namebut runningocis service_namealready works.I suggest we make this consistent and only allow
ocis run service_name.Also:
ocis run xxwill not show an error even though the service does not exist.refs commentedon Mar 19, 2020
The issue is
runis part of the micro runtime, and services to be ran by micro work on a way I'm not fond of; run command requires a folder with go source files, micro runtime will then build them and run it on its own process tree. We bypass this by adding our own commands, and instead of controlling the process lifecycle with micro runtime, we do create a runtime but run out ownocis service_namecommands.I imagine a solution more aligned to building our own process tree and control its lifecycle with it instead.
refs commentedon Mar 19, 2020
@PVince81 for more context: https://micro.mu/docs/runtime.html
[-]cannot manage running services with `bin/ocis ps|kill`[/-][+]cannot manage running services with `bin/ocis run|ps|kill`[/+]Merge pull request #77 from owncloud/dependabot/npm_and_yarn/elliptic…
Merge pull request #77 from butonic/allow_different_namespaces
Merge pull request #77 from owncloud/die-on-invalid-config
refs commentedon Jan 12, 2021
For this we have refs/pman. We don't use go-micro runtime.