Scott Lamb fda7e4ca2b add concept of user/session permissions ... (I also considered the names "capabilities" and "scopes", but I think "permissions" is the most widely understood.) This is increasingly necessary as the web API becomes more capable. Among other things, it allows: * non-administrator users who can view but not access camera passwords or change any state * workers that update signal state based on cameras' built-in motion detection or a security system's events but don't need to view videos * control over what can be done without authenticating Currently session permissions are just copied from user permissions, but you can also imagine admin sessions vs not, as a checkbox when signing in. This would match the standard Unix workflow of using a non-administrative session most of the time. Relevant to my current signals work (#28) and to the addition of an administrative API (#35, including #66).		2019-06-19 15:34:20 -07:00
..
build.sh	simplify and fix installation instructions	2018-08-24 20:45:46 -07:00
clean.sh	Rewrite of the installation script and accompanying documentation. (#15)	2018-03-03 06:41:15 -08:00
install.sh	add concept of user/session permissions	2019-06-19 15:34:20 -07:00
script-functions.sh	upgrade rusqlite, bump required Rust to 1.33	2019-05-31 16:19:04 -07:00
setup-ubuntu.sh	try upgrading travis-ci setup to xenial	2018-12-29 12:21:57 -06:00