Importing nameko.cli.run to execute run()
See original GitHub issueIs it ok to use nameko.cli.run.run()
from my code directly? I want to give nameko some configurations programmatically, using dynaconf, but I do not like the idea of copying and pasting (or “adapting”) the contents of a run function in my program.
Is nameko.cli.run.run()
safe to import, or it is not guaranteed to maintain the interface?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Key Concepts — nameko 2.12.0 documentation - Read the Docs
This command will discover Nameko services in the given module s and start running them. You can optionally limit it to specific ServiceClass...
Read more >Proper serviceRunner usage - Nameko
I'm trying to figure out how to use the serviceRunner and I have a lot of questions. More than answers. my first example...
Read more >nameko - Read the Docs
Nameko ships with a command line interface to make hosting and interacting with services as easy as possible. Running a Service. $ nameko...
Read more >Nameko - invoking RPC method from another service
... is # running, i.e. until you're inside an executing method # y.foo() ... If you want to call a running service from...
Read more >wp import | WP-CLI Command
Provides a command line interface to the WordPress Importer plugin, ... --exec=<php-code>, Execute PHP code before running the command (may be used more ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ll try to make those changes and create a PR.
Sorry for the late reply here @gpkc. You’re right that things are messy. These facilities have independently evolved and never been refactored into a neater place.
I would welcome a PR that incorporated
run_services
intonameko.cli.run.run()
and perhaps also moved the whole lot to a better named module likenameko.run
.There is also the
ServiceRunner
class which is really just a convenience wrapper around multipleServiceContainers
. I’m not overly keen on it. I don’t think it’s really necessary and it could certainly be better named (ServiceContainerCollection
perhaps, although that’s a bit long)