Project:Tool Access Control/ACServer: Difference between revisions

Project:Tool Access Control/ACServer (view source)

Revision as of 16:50, 4 August 2018

120 bytes added , 4 August 2018

update with the current state of play.

JasperWallace

Administrators

1,103

edits

@@ Line 1: / Line 1: @@
 == Summary ==
-ACServer is the access control server that is used by ACNodes (work it out!) to query weather the owner of a presented rfid card has access to the tool and what level of access he/she has. The codebase lives on our [https://github.com/londonhackspace/acserver github repo].
+ACServer is the access control server that is used by ACNodes (work it out!) to query weather the owner of a presented rfid card has access to the tool and what level of access he/she has. The codebase lives on our [https://github.com/londonhackspace/acserver-django github repo].
 == TODO ==
-* All [https://github.com/londonhackspace/acserver/issues issues] on the ascerver repository.
+* All [https://github.com/londonhackspace/acserver-django/issues issues] on the ascerver repository.
-* Code a web ui for adding tools/maintainers/nodes (mentar+levi?)
 == Current deployment ==
-* acserver:1234 current install, purpose built VM running on lamarr.
+* acserver:1234 current install, purpose built VM running on landin.
-* babbage:1234 legacy install only used by the 3-in-1 acnode, which was the first revision
 == Troubleshooting ==
-The acserver permission database is synced with our membership database every minute and leaves a heartbeat at /var/log/acserver_update.log. So check the last modified stamp on that and if the heartbeat is returning 1
+The acserver permission database is synced with our membership database every XXX minutes.
-The application itself is in /var/www/acserver and relies on the local mysql database to work properly also it uses the nginx webserver (leaner, quicker than apache2) so make sure that is running too
+The application itself is in /var/www/acserver and relies on the local postgres database to work properly also it uses the nginx webserver so make sure that is running too.
+Deployment of the acserver-django code is managed by the hackspaces ansible playbook, don't edit anything directly on the VM!
+Useful logs:
+`/var/log/acserver/django.log`: logs from the django code
+`/var/log/nginx/acserver_1234_access.log`: logs from the port 1234 listener on nginx, useful for checking what nodes are doing, the other nginx logs in that directory are useful.
 == Web UI improvement ==
 === Requirements ===
-* Authenticate the user (best done by extending the current member website [https://github.com/londonhackspace/hackspace-foundation-sites codebase])
+This all needs checking against the current state of the code. The acserver-django code uses the hackspaces LDAP infrastructure for authentication and checks group membership(?) for (?).
 * For users with no permissions:
 ** Look up the state of the tools and if they are currently in use