HN user

krishnasrinivas

367 karma

https://nutty.io. Ex-Glusterfs developer.

Posts9
Comments37
View on HN

Absolutely, our focus currently is on multi-server minio which is being actively developed on the "distributed" branch https://github.com/minio/minio/tree/distributed

Our current stable version can export single disk or multiple disks (using erasure coding providing protection against disk failures) As it is very easy to get started with (single binary, thanks to Go) people find it attractive for dev/test environments.

To replicate for HA (even for the single server version), use "mc mirror -watch SOURCE TARGET" command to pair them up. If you have multiple drives (JBOD), you can eliminate RAID or ZFS and use Minio's erasure code to pool them up. Distributed version is also in dev/testing at the moment. It should be out in a month.

It will be useful for any situation where you want to quickly share your terminal. Have you used tmux/screen tools? Nutty will be useful in similar situations where tmux/screen is used but nutty works even if the peer is behind firewall. Plus you can use webrtc when sharing terminals using nutty as it runs in the browser.

I had done "rm" of a big log file to free up space on the customer's server but our process kept on filling the log file. I assumed that the disk has got enough free space and I got busy with something else. The space was never freed up as the file descriptor was kept open by the process. Ultimately the entire disk got filled up by the opened log file and their server came to a grinding halt. I think the customer stopped using our product after that because we never heard from them again.

learning from this experience: never do an "rm" on the log file, instead do "truncate -s 0" on the log file.

Right. home page is of no use if extension is not installed. So it redirects to /info. Once you install extension and nutty scripts you can visit home page to start/share terminal. This behavior is intentional.

Nutty is written in angularjs ... i do routing internally on the client side, so it is supposed to intelligently change the route (address URL) depending on whether extension is installed or not. Did it do something unexpected?