aboutsummaryrefslogtreecommitdiff
path: root/lockchain-http (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Fixing documentation test casesKatharina Fey2018-09-161-1/+1
|
* A lot of refactoring in lockchain-filesKatharina Fey2018-09-151-2/+2
|
* Removing deprecated `UserStore` and `KeyStore` into new `users::UserStore`Katharina Fey2018-09-061-1/+1
| | | | and fixing all resulting code issues
* More refactoring and trying to get keystores to work properlyKatharina Fey2018-08-061-1/+1
|
* (cargo-release) start next development iteration 0.4.1-alpha.0Katharina Fey2018-07-121-1/+1
|
* (cargo-release) version 0.4.0Katharina Fey2018-07-121-1/+1
|
* Changing a bunch of version numbers around. This is really not a good solutionKatharina Fey2018-07-121-2/+1
| | | | | I need a script that can do this automatically for releases because it's getting REALLY annoying and time consuming...
* Bumping versions, updating dependenciesKatharina Fey2018-07-121-1/+1
|
* Adding an example of how to register a user and adding new metadataKatharina Fey2018-07-102-11/+87
| | | | 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-093-301/+244
| | | | Error system (all stubs for now)
* Refactoring the error modules to now contain sub-error typesKatharina Fey2018-07-093-17/+39
| | | | | This isn't ideal yet but good enough for now. Errors can be added via a new variant in lockchain::errors::Error easily
* Removing generics from error typesKatharina Fey2018-07-032-6/+21
|
* Throwing stuff against wallsKatharina Fey2018-07-025-296/+324
|
* This doesn't workKatharina Fey2018-07-024-49/+39
|
* Big code change & refactoring commitKatharina Fey2018-07-021-6/+3
| | | | | | | | | Move `token` into user module for lockchain-core. Start work on a PAM authentication module which replaces the second layer UserStore in API layer state (http being the only one for now). This brings the `nix` and `pam-auth` dependencies, which unfortunately currently don't work :(
* Refactoring models module, adding more inputsKatharina Fey2018-07-015-19/+94
|
* Fleshing out REST API fully and adding function stubsKatharina Fey2018-06-303-27/+130
|
* Ironing out some problems with the ApiState serialisationKatharina Fey2018-06-301-15/+3
|
* Adding more utility functions to a bunch of placesKatharina Fey2018-06-301-4/+19
| | | | Integrating the userstore into the http crate
* Fixing a bunch of syntax errors in the codeKatharina Fey2018-06-224-8/+7
|
* Bumping all dependenciesKatharina Fey2018-06-223-1/+16
|
* Bumping version numbers collectivelyKatharina Fey2018-06-131-2/+2
|
* Refactoring http API and making "not working" routes return a more ↵Katharina Fey2018-06-134-14/+47
| | | | descriptive json
* Working on the http layer, adding 'create' routeKatharina Fey2018-06-124-29/+151
| | | | | | | | | | | | | | | | | | | | | | | | | | 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-123-15/+90
|
* Adding /api and /vault endpoints as first working routes ✨Katharina Fey2018-06-123-5/+48
|
* Bumping lockchain-core versionsKatharina Fey2018-06-121-1/+1
|
* Bumping other crate versionsKatharina Fey2018-06-101-1/+1
|
* Removing User & Login traits from core, adding a metadata store to take ↵Katharina Fey2018-06-103-2/+16
| | | | their place
* Adding a version prefix to all API routesKatharina Fey2018-06-101-13/+14
|
* Fixing documentation formatting :)Katharina Fey2018-06-101-11/+11
|
* Adding documentation for the REST API (to be)Katharina Fey2018-06-101-1/+71
|
* Bumping version numbersKatharina Fey2018-06-091-1/+1
|
* Tweaking the documentation for lockchain-httpKatharina Fey2018-06-092-18/+18
|
* Bumping and updating crate versionsKatharina Fey2018-06-091-2/+2
|
* Updating http documentationKatharina Fey2018-06-091-22/+40
|
* Tweaking the lockchain-http API, adding some constraints on vault traitsKatharina Fey2018-06-093-52/+60
|
* Working on lockchain integrationKatharina Fey2018-06-094-7/+13
|
* Refactoring http libraryKatharina Fey2018-06-092-6/+15
|
* Patch release (cargo release is broken!)Katharina Fey2018-06-071-1/+1
|
* Adding more documentationKatharina Fey2018-06-072-6/+19
|
* Starting work on the lockchain-http interface libraryKatharina Fey2018-06-076-117/+115
|
* A bunch of code changesKatharina Fey2018-06-075-37/+144
|
* Starting work on http crateKatharina Sabel2018-05-133-0/+4
|
* Fixing the manifest filesKatharina Sabel2018-05-111-1/+1
|
* Adjusting version numbers across the ecosystem to bring them all to the same ↵Katharina Sabel2018-05-111-1/+1
| | | | level
* 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-083-8/+21
|