Skip to content
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

How hard to restore FUSE functionality? #43

Open
sethcohn opened this issue Aug 14, 2017 · 3 comments
Open

How hard to restore FUSE functionality? #43

sethcohn opened this issue Aug 14, 2017 · 3 comments

Comments

@sethcohn
Copy link

I realize you removed it... and looking at it, I wonder if it would still be possible to use it with WebREPL or only local ports?

@wendlers
Copy link
Owner

It is not too hard, but I removed it because I don't had (and still don't have) the time to maintain it. Since the FUSE thing used the same python classes as the shell, it would in theory work with all protocols supported by the shell.

@sethcohn
Copy link
Author

I've got it working with WebREPL, it could use some improvements but it functions as expected.

Minor changes to code to get it working (I'll commit something once I'm happy with it to my fork, but if you are open to a PR, let me know.)
(I commented out the .terminal, due to serial assumptions, had to remove the default in .commit, and change 'port' to 'constr' (since it's now doing more than just a port)
But really, relatively painless. I was able to fuse mount an ESP8266 board onto a local directory, edit boot.py using nano, echo "boot.py" > .commit, close the mpfmount, and the altered boot.py was live on the board. Very slick indeed.

@wendlers
Copy link
Owner

sounds good. would be happy to receive a PR as far as you happy with your results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants