aboutsummaryrefslogtreecommitdiff
path: root/lockchain-http/src/lib.rs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* A lot of refactoring in lockchain-filesKatharina Fey2018-09-151-2/+2
|
* Adding an example of how to register a user and adding new metadataKatharina Fey2018-07-101-9/+8
| | | | vault endpoints functions
* Adding the http ability to register/login and managing metadataKatharina Fey2018-07-101-0/+25
|
* Restoring the API handlers again, making it all work with the newKatharina Fey2018-07-091-44/+44
| | | | Error system (all stubs for now)
* Throwing stuff against wallsKatharina Fey2018-07-021-44/+44
|
* This doesn't workKatharina Fey2018-07-021-8/+0
|
* Refactoring models module, adding more inputsKatharina Fey2018-07-011-1/+1
|
* Fleshing out REST API fully and adding function stubsKatharina Fey2018-06-301-15/+52
|
* Fixing a bunch of syntax errors in the codeKatharina Fey2018-06-221-3/+1
|
* Refactoring http API and making "not working" routes return a more ↵Katharina Fey2018-06-131-4/+4
| | | | descriptive json
* Working on the http layer, adding 'create' routeKatharina Fey2018-06-121-8/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | Many things here are not ideal. There is very little checking that's being done, for this we need to tweak the core API a bit further. There are some corner cases that aren't caught. Authentication isn't being done yet. And it's not 100% clear yet where those scopes should live. But...there is progress being made. The API will develop and hopefully soon-ish we'll also be able to add versioning via a new serde-versioning crate being written (hint hint). The basic problem is that we need to build a system that works for two kinds of settings: remotely, administered via a few users, on a different computer with limited access and local, used by a single user and application stack (http interface for browser plugins, file API for everything else). The latter is the focus of development for now, but before we hit 1.0 (aka stable for production) there are more issues to be resolved. Also...if lockchain is to be used as a keystore in poke, we need to figure out how to allow easier integration of the core storage components into other applications (maybe some guides). Also...all of this should be documented in other places than just my ramblings in commit messages 😅
* Starting work on lockchain-http scope filesKatharina Fey2018-06-121-8/+13
|
* Adding /api and /vault endpoints as first working routes ✨Katharina Fey2018-06-121-1/+5
|
* Removing User & Login traits from core, adding a metadata store to take ↵Katharina Fey2018-06-101-2/+7
| | | | their place
* Tweaking the documentation for lockchain-httpKatharina Fey2018-06-091-13/+13
|
* Updating http documentationKatharina Fey2018-06-091-22/+40
|
* Tweaking the lockchain-http API, adding some constraints on vault traitsKatharina Fey2018-06-091-36/+37
|
* Working on lockchain integrationKatharina Fey2018-06-091-6/+9
|
* Refactoring http libraryKatharina Fey2018-06-091-6/+6
|
* Adding more documentationKatharina Fey2018-06-071-6/+14
|
* Starting work on the lockchain-http interface libraryKatharina Fey2018-06-071-0/+49
|
* A bunch of code changesKatharina Fey2018-06-071-31/+0
|
* Starting work on http crateKatharina Sabel2018-05-131-0/+4
|
* Changing the way that vault traits workKatharina Fey2018-05-081-1/+15
|
* More crate metadata for crates ioKatharina Fey2018-05-081-0/+9
|
* Adding dependencies to http crate and publishing itKatharina Fey2018-05-081-7/+4
|
* Massively refactor repositoryKatharina Fey2018-05-061-0/+7