4gig.

 

If I was to take a guess, it probably was a hanging process that was stopping the GUI from coming up as the shares where still accessible.

 

not to mention speeding_ant is NOT a lime-tech employee, just a stand up guy pitching in, really shows how dis-respectful some people can be.

 

Agreed... You entirely missed the point of those messages... Read them again before you start accusing your fellow forum members of being disrespectful.

Which webgui are you both using? Stock, this new webgui or simplefeatures? I've personally since removing SF have never had it hang.

 

What I have found though is that you have to let whatever it is that made it hang finish and then it will come back. So for example if I click on a parity check, I have to let the system initialise the parity check before I can then click on anything else. That even includes any plugins I have running... It's difficult to explain in words, so sorry about that. An interesting test (perhaps?) would be to see that if it happens again, leaving it for a couple of hours and see if it does come back or it truly has crashed. I know that's not very scientific and I'm sure there are better tests to perform, but every time it did hang my system would eventually come out of it.

 

Guys, his father passed away. Is it too much to show respect, stop the nagging and give him the time he needs? He'll come around and resume work.

 

This is an unfair statement to make, as of course this trumps any work being carried out on unRAID. At the time that information wasn't widely known (and still isn't), but is does however reinforce the importance of communication and is all one asked.

 

i'm using SF on mine - with 4GB of ram. sucks that it happens in final also. i'm guessing at some point when the issues about the new gui are sorted out, it'll all work nice. for what it's worth, UnMenu still works when this happens so I can safely shutdown/reboot. good to have options.

i'm using SF on mine - with 4GB of ram. sucks that it happens in final also. i'm guessing at some point when the issues about the new gui are sorted out, it'll all work nice. for what it's worth, UnMenu still works when this happens so I can safely shutdown/reboot. good to have options.

 

+1 ,

using 8GB and it occasionally does the same. I have AirVideo, Control Panel, Plex, Transmission, CouchPotato, SickBeard, and Folder Cache all running.. But i stop services that i dont use all the time while server sits idle.... usually dont have many issues, but when they do its great to have unmenu, screen, or putty to try to restart services or do a clean shutdown and reboot...

Can someone tell me how to update from github?

 

Thanks.

To those of you currently using SF, does the lock out happen often? I am considering trying it out and wanted to know how much of a pain it would be. To fix it all I would have to do is log into unmenu and reboot the server or is there a command?

Any progress on the webgui itself? Would love to have the stats from SF e.g.

Any progress on the webgui itself? Would love to have the stats from SF e.g.

 

Doesn't look like it, me thinks this gonna be a long long slow process of updates if any

 

Really waiting for the sleep and mail plugins

Yeah, i can't imagine it would take so much time to convert some of the existing SF plugins to make them compliant to the v5 gui... They don't have to be built from scratch. And especially now SpeedingAnt and Tom are both involved, troubleshooting etc is much easier.

 

@Tom, @SpeedingAnt, is there a roadmap for the webgui?

Yeah, i can't imagine it would take so much time to convert some of the existing SF plugins to make them compliant to the v5 gui... They don't have to be built from scratch. And especially now SpeedingAnt and Tom are both involved, troubleshooting etc is much easier.

 

@Tom, @SpeedingAnt, is there a roadmap for the webgui?

It is not so much Tom's job to port the other things from simple features over to the new GUI.  The new GUI is essentially a CSS skin on what existed before to make it look prettier.  I'm not saying there was not a lot of work that went into it but the new GUI Tom put up on github is a CSS skin.

 

It will be sppedingant's or whomever picks up where he started to move the remaining features from simple features over to the new GUI.  He has already stated that he is busy doing other things right now and that it would have to wait.

Is the plan still for unRAID to move this this new GUI?  It doesn't look like there's been any activity over on github for a couple months.

 

Is there a page that explains the benefits of the new GUI?  Based on prostuff1's message, it sounds like it won't deal with the problem of the existing web admin page being pretty finicky about only handling one request at a time.  Is it just prettier, or does it offer some other features?

 

Also, is there a way to uninstall it?  Do you just delete webGui-latest.plg?

Also, is there a way to uninstall it?  Do you just delete webGui-latest.plg?

 

Yes, and plugins/webGui-latest.txz

After I installed the webgui plugin, the update button is gone.  So I guess I have to manually go check for updates now??

 

What is the current webgui version?  Mine shows ...r3 in the lower right hand corner.

The Update button only exists in the old GUI and is used to install the new GUI. The new GUI does not currently have an update feature; you'd have to copy a newer version to your USB drive to update it.

 

The new GUI was put on GitHub presumably with the thought that others could help with it's development but Limetech has to authorize these changes and hasn't made any updates of their own as of yet; nothing has changed since the initial release.

 

You can see the status at https://github.com/limetech/webGui and see if it's been updated (I'm sure there will be a post here as well).

 

Cheers,

...Donovan

I need to start staging some changes to the webGui code base on github.  This exact question on stackoverflow.com asks the same question I have:

http://stackoverflow.com/questions/8461528/github-is-it-possible-to-replace-the-entire-repo-and-keep-the-issues-etc

 

What do you think, is the answer posed there the "right" way?

I need to start staging some changes to the webGui code base on github.  This exact question on stackoverflow.com asks the same question I have:

http://stackoverflow.com/questions/8461528/github-is-it-possible-to-replace-the-entire-repo-and-keep-the-issues-etc

 

What do you think, is the answer posed there the "right" way?

 

As long as there is a backup, seems like a fair option. Can always ask github themselves.

You might as well keep the current state of the github available as a separate branch..

 

From the working directory of the current version:

 

git checkout origin/master
git checkout -b old_state
git push origin old_state

 

Then reset master by following that stack overflow comment.

really you should have a branch for whatever code you wanna do.. i'm assuming your going to have a webgui for 5.x and one for 6.x ?

you can do this two different ways,

 

1 repo for each trunk code, so webgui-5 and then webgui-6, keeps them separate but does require double the work.. but if your not really going to be making changes to the gui for 5.x as  most efforts i would assume would be directed towards 6.x.. then this may be overkill.

 

you could just have 1 repo as you currently do, and just have the 'master' branch would be the latest 5.x code... you just make a new branch based off 'master' where you can go modify it to your heats content for 6.x. then when your ready you push down master. the key is that you never push to master directly since other branches are based offf it.. you push to 5.x or 6.x then pull down into master from them.

 

if you want to maintain two separate forks of code.. like 5.x in case you want to push out updates later for that.. you just keep that in its own branch. kinda like what we do for sabnzbd

https://github.com/sabnzbd/sabnzbd/branches

 

'master' is the latest code for the current trunk.. 0.7.x. develop has 0.8.x. when we need to make a new update to 0.7.x we put the new code there then push down to master. this keeps 'master' more like a stable branch.. allows us to test code and keep the code diversions to a minimum.

 

http://nvie.com/posts/a-successful-git-branching-model/

 

 

Assume this is abandoned?  New release breaks it anyway.  After stopping the array an error appears and you can't shutdown.

Assume this is abandoned?  New release breaks it anyway.  After stopping the array an error appears and you can't shutdown.

Not abandoned, will be updating soon.

Not abandoned, will be updating soon.

 

Great!  Look forward to it. 

Is the current Version of the new webGUI compatible with unRaid 5.0.2 or do i run into problems when i am updating for 5.0 final?

Is the current Version of the new webGUI compatible with unRaid 5.0.2 or do i run into problems when i am updating for 5.0 final?

Assume this is abandoned?  New release breaks it anyway.  After stopping the array an error appears and you can't shutdown.

Not abandoned, will be updating soon.

 

From the above quote by limetech, I'd say the new webGUI is not ready for production yet.

simple request, can the uptime be moved back onto the main page just as it was in simplefeatures? PLEASE!?!

Just a (silly) Question:

Whats going on with this GUIs???

Simple Feature is dead and this "new" GUI is not working???

Did all programmes leave Lime Tech alone or what?

It seems for me, that this change to GitHub was a bad decision

Can someone give me a "clear" statement of this GUI-Chaos - thanks