[Suggestion] Web-UI for headless devices like NAS etc.
-
- Posts: 2
- Joined: Fri Jun 15, 2012 6:58 pm
[Suggestion] Web-UI for headless devices like NAS etc.
Hello,
i use UMS aka PS3MS since 2 jears now on my ReadyNAS x86 device. It runs very stable and does the things i want to.
But to configure it is very complicate to open the configfile with an unix capable editor without any help about syntax or alernatives.
Why not use the buildin webserver to configure UMS?
It would be a great thing to do these configs with a webinterface or a external console like serviio has.
I know, this is not a fresh idea but it is a good idea.
cu
Martin
i use UMS aka PS3MS since 2 jears now on my ReadyNAS x86 device. It runs very stable and does the things i want to.
But to configure it is very complicate to open the configfile with an unix capable editor without any help about syntax or alernatives.
Why not use the buildin webserver to configure UMS?
It would be a great thing to do these configs with a webinterface or a external console like serviio has.
I know, this is not a fresh idea but it is a good idea.
cu
Martin
Re: Web-UI for headless devices like NAS etc.
Yeah that is a good idea 

Re: Web-UI for headless devices like NAS etc.
I would love to see a Web Interface piece for PMS.. think about using the Browser on PS3 to start stop the app or make changes on the fly that way.
One step further would be to Stream over Web Server to client.
Take requested file, put into a live streaming page, and present to user. It would be awesome.
One step further would be to Stream over Web Server to client.
Take requested file, put into a live streaming page, and present to user. It would be awesome.



Please remember to Upload your debug logs!
Universal Media Server Wiki!
"...functionality before beautification..."
Re: Web-UI for headless devices like NAS etc.
As a web developer I could help with the frontend (HTML/JavaScript) but there would have to be some kind of basic http server functionality. Perhaps just as simple as creating a way to modify the configuration files like this:
This would be an example URL to set the ac3 auto bitrate to 348.
As long as the keys are unique (not like "Supported" in the renderer conf files). This should work well and doesn't require code modifications for any new features on the server side. And we could make a nice HTML/CSS GUI around it.
However this should be only for initial configuration. For all the things, that need to be changed on-the-fly I think the #Video-Settings# folder is much cooler. I wouldn't want to use the web browser of my renderer for this.
Code: Select all
http://192.168.0.2/writeconfig?key=audiobitrate&value=348
As long as the keys are unique (not like "Supported" in the renderer conf files). This should work well and doesn't require code modifications for any new features on the server side. And we could make a nice HTML/CSS GUI around it.
However this should be only for initial configuration. For all the things, that need to be changed on-the-fly I think the #Video-Settings# folder is much cooler. I wouldn't want to use the web browser of my renderer for this.
Re: Web-UI for headless devices like NAS etc.
Please see my feature request "REST API" which would be a standardized way to implement such functionality.
The Web-UI could be built on top of that API. Serviio has such an API available - see here.
With such an API available web developers could implement frontend / configuration utilities with any language ( PHP, Ruby ... even pure JavaScript as a Bookmarklet ... )
@Jeymz
Your solution http://192.168.0.2/writeconfig?key=audi ... &value=348 is a good idea but kind of wrong in terms of web standards for setting data ( as a GET request would be used to set/change data ).
Ideally one would use a PUT/PATCH/POST request to http://192.168.0.2/config but the general idea is awesome
The Web-UI could be built on top of that API. Serviio has such an API available - see here.
With such an API available web developers could implement frontend / configuration utilities with any language ( PHP, Ruby ... even pure JavaScript as a Bookmarklet ... )
@Jeymz
Your solution http://192.168.0.2/writeconfig?key=audi ... &value=348 is a good idea but kind of wrong in terms of web standards for setting data ( as a GET request would be used to set/change data ).
Ideally one would use a PUT/PATCH/POST request to http://192.168.0.2/config but the general idea is awesome

Re: Web-UI for headless devices like NAS etc.
I completely agree. Using GET here may lead to all kinds of problems, e.g. when going back in browser history. I was just trying to keep it short and simple.nicomess wrote:Your solution http://192.168.0.2/writeconfig?key=audi ... &value=348 is a good idea but kind of wrong in terms of web standards for setting data ( as a GET request would be used to set/change data ).
Ideally one would use a PUT/PATCH/POST request to http://192.168.0.2/config but the general idea is awesome
Standard API sounds great to me, but can't help you there, sorry
