You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jiangliu and @sameo were asking/suggesting to publish our micro_http implementation to crates.io.
I am opening this issue to discuss if this is something that we want to do. I don't believe that rust-vmm is the appropriate organization for this crate as the micro_http is not really related to VMMs, so we will need to be hosting it in some other place.
Thanks Andreea:)
I have done some experiments and worked out a draft version of micro-http crate, which combines code from both firecracker and cloud hypervisor.
So it would be great if we could cooperate on this topic to build a light-weight and secure http implementation:)
On Jan 14, 2020, at 2:40 AM, Andreea Florescu ***@***.***> wrote:
@jiangliu and @sameo were asking/suggesting to publish our micro_http implementation to crates.io.
I am opening this issue to discuss if this is something that we want to do. I don't believe that rust-vmm is the appropriate organization for this crate as the micro_http is not really related to VMMs, so we will need to be hosting it in some other place.
CC: @firecracker-microvm/compute-capsule
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
@sameo@jiangliu we created a repository with the micro-http code in the firecracker-microvm organization. We plan to move this at some point to an organization where it makes more sense to sit, but to kick start things faster, we can consume the micro-http implementation from there for now.
We will also open an issue with what we think are the next steps before publishing it to crates.io. In the meantime, can you also open issues/PRs with the changes that you had in mind so we can sync on it?
Is there any blocker for this issue? I am looking into packaging cloud-hypervisor for Fedora but it depends on this crate using a git dependency (which goes against the packaging guidelines). Would really appreciate this crate getting published on crates.io.
Activity
jiangliu commentedon Jan 14, 2020
andreeaflorescu commentedon Jan 27, 2020
@sameo @jiangliu we created a repository with the micro-http code in the firecracker-microvm organization. We plan to move this at some point to an organization where it makes more sense to sit, but to kick start things faster, we can consume the micro-http implementation from there for now.
We will also open an issue with what we think are the next steps before publishing it to crates.io. In the meantime, can you also open issues/PRs with the changes that you had in mind so we can sync on it?
dianpopa commentedon Mar 10, 2020
Would it make sense to open this issue in the newly created repo?
andreeaflorescu commentedon Mar 10, 2020
@dianpopa Issue is now transferred to the micro-http repo.
dianpopa commentedon Mar 10, 2020
Cool, thanks!
stappersg commentedon Apr 26, 2020
The sole purpose of this update is to give this issue some puls. The idea is that it gets moving again.
KarthikNedunchezhiyan commentedon Nov 19, 2020
@andreeaflorescu Is there any near future plan for publishing this as a crate ?
blinxen commentedon Aug 31, 2026
Is there any blocker for this issue? I am looking into packaging cloud-hypervisor for Fedora but it depends on this crate using a
gitdependency (which goes against the packaging guidelines). Would really appreciate this crate getting published on crates.io.