Locker Internals: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
< [[Main Page]] < [[Carbon Commute]] | |||
---- | |||
Locker was a project by San Francisco startup [https://singly.com Singly] which is now no longer maintained. More information about the former project can be found at http://lockerproject.org. The code can be found at https://github.com/LockerProject/Locker. | Locker was a project by San Francisco startup [https://singly.com Singly] which is now no longer maintained. More information about the former project can be found at http://lockerproject.org. The code can be found at https://github.com/LockerProject/Locker. | ||
Latest revision as of 17:12, 29 January 2013
Locker was a project by San Francisco startup Singly which is now no longer maintained. More information about the former project can be found at http://lockerproject.org. The code can be found at https://github.com/LockerProject/Locker.
The locker code was forked and patched to fix bugs in the existing project, and can be found at https://github.com/elsmorian/Locker
The locker provides both an API interface to allow data upload and access, and supports internal applications that run within the locker, that interact with the aforementioned API.
Each locker runs multiple API endpoints, on of which allows the push of data into the locker. This endpoint is used by the Carbon Commute app after each commute is complete, to push a JSON object into the personal container. This JSON object represents each commute, and contains metadata such as the start and end of the commute, along with an array of GPS points.
