speeding_ant
Members-
Posts
1,624 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by speeding_ant
-
This worked great, did my.ip.address:90 and it worked. One thing I would suggest is that available size on disks is per TB, so even if only 50GB are taken on a 2TB drive it says it has 1tb free, i guess it does not specify to decimal places. Not sure if that is something that will be coming? Thanks for the heads up, that will be fixed in the next release.
-
Just a quick progress update! There is progress being made, and we're into the second round of beta testing. Latest release notes below: Features Added: • Detection of parity check, added percent complete in array status window • Shut down and restart server in menu item (only available if array is stopped) • Warning before turning off array, shutting down, or restarting server. • Auto-resize of window based on amount of disks /shares present. This will max out at 10 disks / shares, at this point you will need to scroll further. • Cache drive appears after Parity in Disks view Bug Fixes: • Fixed icon colour preference checkbox • Connecting view is more stateful • Now you cannot select tabs while in edit server or preferences view • Misc reliability improvements, and removal of debug code
-
Almost there - I just need a couple of beta testers. My requirements are: • Arrays larger than 6 drives • Running 10.8, and 10.9 • unRAID 5+ Please PM me if your setup matches the details above, with an email address so I can contact you. Please do not be angry if I do not choose you, you'll get to use the app soon anyway. Cheers!
-
Works out of the box! If you have a password set via the webGUI, the app will require a password to be set up before the it can connect. Due to the fact unRAID does not use SSL, the credentials would be sent 'non securely' across the network via http. This is the same behaviour the browser would use if you authenticated to the webGUI. Without SSL on the server side, there is nothing more I could do here without adding a huge amount of complexity.
-
Thanks for the comment! I'd rather not limit myself to Firefox users either ;-) I'm writing a native OS X App because: • I want to make something sexy • The code is relatively easy to port to iOS • I want it accessible anywhere, without the need for a browser • Cocoa is relatively lightweight, asynchronous and powerful, with ties to notification centre and other useful API's • I want to make something sexy I'm connecting in special ways that are fast :-)
-
Hackintosh won't be a problem, I run one too. I will only support 10.8+ at the time being, mainly due to some of the API's I'm using. If there are enough sales to make it worth while, I'll re-write the API's to support 10.7. To give you guys an idea of the progress... last night I finished the main GUI, navigation, and error checks with notification centre support. Over the next couple of days I should have the GUI and data model for storing the server login information finished, including storing the password to your secure login keychain. Another question! When the app detects any drive / temp errors (with temp limits you can specify), the primary pie graph will turn red. The menu bar icon will turn red. The drive in question will have it's background row turned red. You will receive a notification for it ONCE, unless any of the variables change (i.e. if the temperature goes up further or there are more drive errors). Does that sound like overkill, or is that what you're looking for?
-
Thanks I know what you're saying regarding mapping network drives. Ultimately I'd like this app to auto mount shares, however Apple is far too strict regarding any access to the filesystem in a Sandboxed app. There is no way this could make it to the final feature set without Apple changing something.
-
Cool - glad to see some interest! In terms of notification... if something goes wrong with temp, array or drive errors, the menu icon will go red. You can configure notification centre notifications for each of those three error categories. I'm planning to make this app sandboxed, and available for a small fee in the Mac App store. Naturally any beta testers will get a free copy. I have a couple of comments regarding some of your ideas. I can provide a combined error stat on the main view when you open the app for the first time. Of course, the disks tab will have further detail. This information will be present in the disks tab. Again, would provide a way configure a minimum warning temperature range and display an 'All OK' or similar on the main page. Will see. I wouldn't want any feature creep as it's supposed to be an easy and simple way to see your array stats wherever you are in the OS.