I’m a little too afraid to put the entire compile for LD into the cloud itself – lots of stat() calls on lots of files causes lots of traffic, and the performance hit is a bit rough right now.
#Toshiba macfuse driver full
Took me a while, but I got to where I can do a full compile, rsync, upload – everything – all from LD itself. And then booted up into LightDesktop, with that filesystem available as a secondary FS. Then I moved my LightDesktop dev directory over to a separate filesystem. That compile was actually the root window manager/launcher thing for LightDesktop. I started by making it so that I’m able to compile a relatively simple project, with the storage all living in the Cloud.
![toshiba macfuse driver toshiba macfuse driver](https://sharplesgroup.com/wp-content/uploads/2017/07/toshiba-e-studio-3505ac-large-capacity-feeder-radf.jpg)
Not configurable yet, but that’s probably one of the things that’s next. I also modified the ‘root window manager’ thing – it has a sorta taskbar style doodad, with a wireless strength meter and a battery power meter, and some little quicklaunchey button things. I think I wrote the client side, I just want to do something super wussy on the server end where I don’t delete it ‘just in case’…The new filesystem should have several attributes the old one did not have – it should work disconnectedly, it should be cache-aggressive, it should use the cache when disconnected, it should perform well, and it should have some support for symlinks. I’ll get there, just have to build up the courage. Because I am a fearful little wretch of a man, I did not write the ‘DELETE’ method yet. I’m enjoying it, when I am not feeling like tearing my hair out. It’s nice, writing both the server and client sides of a remote filesystem setup. So – biggest thing is that I’ve replaced the horribly-performing WebDAV with a CREST-fs derived writable filesystem.