Repository navigation
Replies: 2 comments 3 replies
|
It's coming in the next release! 🙂 |
0 replies
|
Hii @BinSquare! , checking in on this , is this currently actively in development on your end, or is there a design / branch i can help take off your plate and build out? I'd love to implement anything i can help with in this |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem & Context
When using
smol upwith[dev] volumes(e.g.volumes = ["./src:/app"]), developers rely on file watchers inside the guest VM (such as Vite HMR, Next.js Fast Refresh,cargo watch, or Python hot-reloaders) to detect code edits.However, standard VirtioFS / 9p mounts do not natively forward host OS file events (macOS
FSEventsor WindowsReadDirectoryChangesW) into Linux guestinotify/fanotifyqueues. Watchers inside the guest either miss updates or are forced to enable polling (CHOKIDAR_USEPOLLING=1/WATCHPACK_POLLING=true), which causes high CPU utilization and adds noticeable latency.Proposed Architecture
Implement a lightweight host-to-guest file event relay:
smol up,smolvmwatches the mounted host directory paths on the host side using the cross-platformnotifycrate.Create,Modify,Delete),smolvmsends a lightweight event message over the vsock connection tosmolvm-agent.smolvm-agentreceives the event and triggers aninotifyping ortouchon the corresponding path inside the guest mount point, allowing guest watchers to react instantaneously with zero polling overhead.Benefits
Would love to hear maintainers' thoughts on whether this direction fits the
smol uproadmap!All reactions