Sexy, Innovative, Cross platform, Nice!
Works as advertised on OS X 10.6.8
For some reason gives me the feel of a DD-WRT GUI, Neat! Focused! Secure! absolutely lovely!
Never going to exit GUI ;)
Sexy, Innovative, Cross platform, Nice!
Works as advertised on OS X 10.6.8
For some reason gives me the feel of a DD-WRT GUI, Neat! Focused! Secure! absolutely lovely!
Never going to exit GUI ;)
Yep completely understand that, however when i installed the x64 version - nothing worked. I installed the x32 versions and everything works correctly. This is on a x64 version server platform. Also i didn't install in the default installation locations - i installed everything in %programfiles(x86)%.
the problem with windows is that the path could have been everywhere, but it cannot determined where using a simple command, certain things are being assumed in the code (ie; hardcoded). win32 will therefore work with default install paths.
Sexy, Innovative, Cross platform, Nice!
Works as advertised on OS X 10.6.8
For some reason gives me the feel of a DD-WRT GUI, Neat! Focused! Secure! absolutely lovely!
Never going to exit GUI ;)
you can exit though; it will determine if the webserver is still running if yes, it will open the same page again (you could bookmark it, but no guarantee it will work everytime)
the problem with windows is that the path could have been everywhere, but it cannot determined where using a simple command, certain things are being assumed in the code (ie; hardcoded). win32 will therefore work with default install paths.
Absolutely true - thats why i run 90% of my Plex setups on linux (Lubuntu) make life easy, however i have just moved from ESXi to Hyper-V and i thought i would through PlexConnect on the Hyper-V host as it is always up and i have more than one Plex server so that way there is always access to whatever server is available.
WOW. Does it work on windows too, i guess?
Only Auto-Upadte and GUI auto update left :)
WOW. Does it work on windows too, i guess?
Only Auto-Upadte and GUI auto update left :)
It works on windows, but with only if you used default install paths for python and with pywin32.
I was working on a version check/update possibility, but there are many exceptions to make it work (especially cross-platform).
Hey Guys,
With the added info of using all default paths it is now working for me.
Is there a way to run setup.py as a service so I dont have to run the batch file every time i want to view
the log to see if Plex Connect is running OK?
Do the services now shutdown and save ATVSettings.cfg? or do i need to force a stop whenever I make a significant change on the user interface?
What does the autostartup plex services feaure do, Add the batch file to the task scheduler? I originally said no to that step but can't go back and re-enable it without running thru the whole setup process again.
Cheers Rob.
Is there a way to run setup.py as a service so I dont have to run the batch file every time i want to view
the log to see if Plex Connect is running OK?
Do the services now shutdown and save ATVSettings.cfg? or do i need to force a stop whenever I make a significant change on the user interface?
What does the autostartup plex services feaure do, Add the batch file to the task scheduler? I originally said no to that step but can't go back and re-enable it without running thru the whole setup process again.
Okay bakman1 keep me honest.....
The idea is to integrate it into PlexConnect's own web server so that the GUI would be accessible all of the time when PlexConnect is still running (it currently uses its own separate one - hence current the "exit GUI" button if you want to kill it).
Also PlexConnect is designed to be pretty much leave alone once installed, especially when installed as a service.
You should hit "save configuration" after making changes, this will shutdown and restart, forcing a save and reload of settings.
Autostart should install PlexConnect as a service (the dependency for running as a service in the official way is the same as the GUI so you should be covered). You can change this at any time by ticking or unticking the "always running" button (maybe the wording on this should be changed to be less ambiguous).
It would be great if you could replace the boring error response screen with this as well.
The "not serving this client"-one?
To further elaborate on f00b4r's comment.
This GUI is basically a (cross-platform) front-end for PlexConnect (stop/start/restart/settings manager and when applicable install plexconnect as daemon).
setup.py will start an additional webserver which provides the GUI
When you close your browser window, the webserver will remain running until you reboot your system (hence the GUI will remain available on the same address).
When you "exit GUI" it will kill the GUI webserver and setup.py must be run again in order to access the GUI.
I was working on (WIN/OSX) apps that could handle the setup.py, but it appears to have some issues to make it work properly for both win/osx. (you can create a batch file to setup.py).
setup.py will determine if the webserver is still running or not.
I’m running Windows 7 64-bit using Python 32-bit and found the following …
Chanigng “python.exe” to run as “Administrator” for all users prior to first running “setup.py” allows the install of the PlexConnect service during the initial start. Remove the comparability change to “python.exe” after the first run for security reasons. This is necessary if you have the default settings for UAC onWindows.
If using iMovie the path shown for the profile on AppleTV is wrong, http://trailers.apple.com/imovie.cer doesn’t work. Changed it to http://www.icloud.com/imovie.cer works a treat.
I now have the PlexConnect service staring automatically during reboot. Changed the recovery option to restart the service. Perhaps a delayed start may be better - yet to try.
Also I’ve created a shortcut on the desktop to “setup.py” which starts the GUI when clicked. I changed the properties of the shortcut to open in a minimised window.
Great work, looking forward to future releases.
Regards
Hi, can get it to work on my Proxmox VM Host. I think its a problem with the Port 8006. Anyone can say me how to change the port? I am Running plexconnect under a openvz container and the Proxmox Host runs his Admin Webinterface on Port 8006. If i load PlexConnect GUI it stops loading ...
ok, resolved. Found it in setup.py. Thanx
doesn’t work for me using win 8.1…the old way still works…
-wont install .cer(iMovie trailer icon) just sits and spins…i tried both address’s…
i have original .cer installed still for trailers icon.
1-output when i change to trailers icon and start service
2-output from initial start
3-output using imovie icon(.cer never added) and start service
This is a wonderful step forward, congrats!
doesn't work for me using win 8.1...the old way still works..
-wont install .cer(iMovie trailer icon) just sits and spins..i tried both address's..
i have original .cer installed still for trailers icon.
1-output when i change to trailers icon and start service
2-output from initial start
3-output using imovie icon(.cer never added) and start service
I didn't test it on W8(.1)
Looking at your screenshots - it appears work, but it's interesting that you get a "cat" error.
That means that the webserver is running or has started in the past.
Try:
del daemon_support.txt daemon_installed.txt connector.txt plexconnect_status.txt
and run setup.py again.
I'm an almost complete noob regarding web development... But I've tried to make some tests in my Syno. It's not difficult to have support/setup/ "working" in the Syno. In fact, it's as simple as saying to the Syno that index.html (and its companion script.js) is the entry point to this code, and modifying some path's in the filenames.
By "working" I mean displaying the index.html page filled with the contents of the Settings.cfg file, and change some parameters. What I could not do is to use the "action" buttons, therefore I could not save the Settings.cfg file.
With my (very little) knowledge I've found that these action buttons are handled by the python process started with setup.py, while in the Syno the index.html file is handled by its Apache process. Is it possible to progress from here to make this code available in Synology ?
how are you starting the webpage on the syno ? just opening the index.html ? that will not work.
you will have to start it on the commandline by ./setup.py and probably manually opening the address.
The actions should work on a synology - the only thing that will (definitely) not work is the daemon-install.
how are you starting the webpage on the syno ? just opening the index.html ? that will not work.
I can access my Syno from a remote PC via http. In the administration page there is an icon that points to another page where I have icons to access all running processes. During the installation of a package (such as the PlexConnect installer built by bwynants) it is indicated (in a config file) the address of the program that will be opened by Apache when a user clicks in the icon of the application. This program can be html, so I've pointed it to your index.html file (I have in the Syno your /support/setup/ folder). I had to modify your html (removing the reference to the process launched by your setup.py, and correcting the path to the various files) and it opened ok.
It is a fact that index.html (or script.js) has read my Settings.cfg file and displayed it correctly. But when I clicked in the "save" button, because I removed the reference to the process launched by setup.py, index.html just refreshed the screen with the info from my original Settings.cfg file (discarding any changes). Also, in the disk of the Syno, the timestamp of the Settings.cfg file did not change. Also, in the Syno, there is a start-stop-status command to start or stop the PlexConnect process, therefore there are some specifics here compared with other platforms.
I think that if index.html / script.js were able to read the Settings.cfg file correctly they should also be capable of writing it, of course with some changes, or am I wrong ?
One of the main differences between a OSX/Windows and Synology is that in the former you are using the same machine where PlexConnect is running, while in Syno there is a server (the Syno itself, where PlexConnect and Apache are running) and a client (Linux/Firefox in my case) in a separate machine. So this is a client/server process, unlike what you have with OSX/Windows.
I hope I've described the process (I'm not a technician, I don't know what a daemon is...).