-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssh deploy and firecracker #725
Comments
|
hey @ripienaar yep a NATS weaver is exactly what I am working on. So then you can just connect over the NATS control plane. I dont know how to reach you :) I am on Telegram though... |
Hey @ripienaar If you have time for a chat about this can you grab me on telegram or suggest what you want to use ? |
Slack is where nats support happens. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
there is a easy way to run firecracker with weaver ssh deploy.
docs: https://docs.nats.io/using-nats/nex
code: https://github.com/synadia-io/nex
This gives you a cloud in a box in many ways.
When you mix weaver with NATS you can orchestrate your "cloud".
I just adding this as an Issue even though its not an issue because the 2 things works so well together IMHO.
The SSH deployer is missing a few things are documented here: https://serviceweaver.dev/docs.html#ssh-experimental-limitations
The NATS Cli can be used to control Weaver, so I might make a "weaver nats deploy" etc ...
Am just thinking out loud here to see if anyone is into this. Would appreciate any feedback about this concept / approach.
The text was updated successfully, but these errors were encountered: