hi,
On Tue, Mar 11, 2014 at 4:08 AM, Domen <[email protected]> wrote: > Hi, > while researching Raspberry PI project more in depth, I have some > questions: > 1. Security: In order to restrict access to REST api, I would need to > implement some kind of user system. > 1.1. What would be better, to provide login interface in REST api, or use > HTTP login (like in auth monkey plugin)? Maybe a combination, provide login > via REST api, but request HTTP login if user is not logged in when > accessing REST api? For HTTP login I would probably have to add support for > it in Duda I/O? > basic auth over SSL should do it fine, its not the strongest but works, or.. you can force some session and login stuff, that will work too. > 1.2. Is there a need for more advanced permission management with groups > of users, or just grant permissions to each user separately? > not really. > 2. While the project is specifically named Raspberry PI Dasboard, most of > the stuff could be used on any linux system (CPU, memory, network,...). > Only few specific things are RPI only (GPIO). Would it not be better to > name the project Linux Dashboard and also provide RPi specific stuff, but > let it be detected at runtime and only enabled if present. > The focus is RPI, despite it can run everywhere it should focus on that because of performance & HW specifics. > 3. The project only talks about hardware resources, but what about > software resources (process management, starting/stoping /etc/init.d > daemons,...)? > We aim to provide a flexible environment for developers using the RPI so they can manage each HW feature. This is not intended for someone running a desktop on it, the focus is "HW/SW developer doing something cool and need a HTTP interface to manage everything" thanks
_______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
