Request: Auto update feature

[zebulon501]

Request: Auto update feature

[N0Klu3]

Bump this.

Having it auto update will make life alot easier.

[rembo10]

For sure. I need to do a lot of reorganizing to make this feature easier to implement but it is coming :-)

[rinkeb]

+1

[typhoe]

+1 too !

Would make our life a lot easier :-)

[tsugliani]

+1

This would be a great feature !

[smosse]

+1
ditto :)

[gugahoi]

Ye this feature is a must. BTW rembo, been waiting on this rewrite. Trying to refrain myself from coding so it doesn't conflict with things you might have rewritten.

[rembo10]

Seems like this is the most wanted feature :-). I'll put it in the next update, just need to work out how I'm starting/stopping threads so it will update smoothly.

@gugahoi - I've been so busy the last couple weeks but I've got a break now so I should have something up soon. I'll get a roadmap up so you can take a look at what I'm working on or may have already written

[frans01]

+1

[gmontard]

+1

[Sholofly]

absolutely +1!

[mikeo999]

+1

[dreamonn]

+1

[lgordon]

+2

[bondar]

+1

[rembo10]

It's definitely coming. I'm kind of juggling around how the program runs to make self-updating possible.

[zebulon501]

Thanks rembo10. It's nice to see that you listen to your users!

[Jiminy68]

+1

thx for your work.

[flyingdutchman31]

+1

[rembo10]

Hopefully I can get it done tomorrow - I just finished reorganizing everything which was the hard part

[flyingdutchman31]

Thats great news. I really look forward to having an automated msic solution

[zebulon501]

Very nice!

[Sholofly]

Sounds good! I'm looking forward to it!

[pilothaz]

pumped to see it tell me there is an update..... well after this update ;)

[rembo10]

How are you guys installing Headphones? Git? Tarball? Zip?

Git

[rembo10]

Alright, I've been busting my ass all day to get this for you guys but I think it's finally done :-)

It'll be up in a few minutes :-)

[dreamonn]

re: installation - zip

Thanks for the effort put into the update

[flyingdutchman31]

Rembo thank you for all the effort you put into it

[rembo10]

It won't work with zips yet, just git installations. That'll change in the next day or so since I have everything organized right.

@Cdouma: No worries!

If you're feeling generous: Donate!

[zebulon501]

To be able to package it for the Synology NAS, I would like it to be independent of any external executable. So I prefer a solution based on a zip or a tarball.

Thanks for the good and quick progress on this point.

[rembo10]

Zip/tarball self-update coming soon, now that I sort of know what I'm doing :-)

[rembo10]

HEY NOW! self-updating works with git, zip and tarball!

Although it doesn't redirect to the homepage after a restart.... I'll work it out though...

[zebulon501]

The update works as expected. I just downloaded the tar.gz file, unpack locally, start it, and request an update from the Web GUI. It work, at least from the Web GUI point of view. When I look at the running processes, it seems your update suffer from the same issue than SickBeard: depending on the underlying thread implementation, stopping the process can only be done from the main thread, not a child one. See http://code.google.com/p/sickbeard/issues/detail?id=1026.

[rembo10]

I think the latest update may have fixed this. There was an issue with a thread staying open if a link was sent to sab that had no track information. I'll double check to see if there are any other issues

On Jul 18, 2011, at 2:16 PM, [email protected] wrote:

The update works as expected. I just downloaded the tar.gz file, unpack locally, start it, and request an update from the Web GUI. It work, at least from the Web GUI point of view. When I look at the running processes, it seems your update suffer from the same issue than SickBeard: depending on the underlying thread implementation, stopping the process can only be done from the main thread, not a child one. See http://code.google.com/p/sickbeard/issues/detail?id=1026.

Reply to this email directly or view it on GitHub:
#28 (comment)

[zebulon501]

@rembo10: I just downloaded the last tar.gz, which includes your latest patches, and run Headphone.py. Then, without any configuration, I requested a restart. A new python process is launched, but the old one is still there. The fix for SickBeard was to terminate the process from the main thread, not from one of the web server worker thread.

[rembo10]

Ah i gotcha. I'm running the shutdown script from within the cherrypy thread.

I'll set up the main thread to listen for signals then terminate all the child threads.

What OS are you on? It works fine on OSX so I may need you to test until it works

On Jul 18, 2011, at 3:02 PM, [email protected] wrote:

@rembo10: I just downloaded the last tar.gz, which includes your latest patches, and run Headphone.py. Then, without any configuration, I requested a restart. A new python process is launched, but the old one is still there. The fix for SickBeard was to terminate the process from the main thread, not from one of the web server worker thread.

Reply to this email directly or view it on GitHub:
#28 (comment)

[zebulon501]

That's exactly the issue, dosing the shutdown from a worker thread.

I'm running on a Synology NAS (Linux 2.6.32, PowerPC). I'll test it as soon as possible (when it is ready, and when I'll have some time).

Any way, thanks for your help.

[Organizer]

Another +1 great to see you adding the update function. Never heard of it before Zebulon posted on his blog, so will DL his Synology NAS package as soon as it's ready and start using :) Great work both..

[beckos]

+1

[Logan09]

Seen this on Zebulon's blog and it looks like just what I need. Can't wait for the autoupdating to be sorted and Zebulon to put out a SPK.

I thought this was fixed, but today I had to kill a few dozen zombie processes (2 for every time I updated HeadPhone from its web interface).

[rembo10]

You're right. This will be fixed in the next update (already fixed in develop branch)

On Aug 12, 2011, at 3:57 PM, [email protected] wrote:

I thought this was fixed, but today I had to kill a few dozen zombie processes (2 for every time I updated HeadPhone from its web interface).

Reply to this email directly or view it on GitHub:
#28 (comment)

[rembo10]

fixed in the latest commit

On Aug 12, 2011, at 3:57 PM, nightspirit81 wrote:

I thought this was fixed, but today I had to kill a few dozen zombie processes (2 for every time I updated HeadPhone from its web interface).

Reply to this email directly or view it on GitHub:
#28 (comment)