aboutsummaryrefslogtreecommitdiff
path: root/lockchain-http (unfollow)
Commit message (Collapse)AuthorFilesLines
2018-09-16Fixing documentation test casesKatharina Fey1-1/+1
2018-09-15A lot of refactoring in lockchain-filesKatharina Fey1-2/+2
2018-09-06Removing deprecated `UserStore` and `KeyStore` into new `users::UserStore`Katharina Fey1-1/+1
and fixing all resulting code issues
2018-08-06More refactoring and trying to get keystores to work properlyKatharina Fey1-1/+1
2018-07-12(cargo-release) start next development iteration 0.4.1-alpha.0Katharina Fey1-1/+1
2018-07-12(cargo-release) version 0.4.0Katharina Fey1-1/+1
2018-07-12Changing a bunch of version numbers around. This is really not a good solutionKatharina Fey1-2/+1
I need a script that can do this automatically for releases because it's getting REALLY annoying and time consuming...
2018-07-12Bumping versions, updating dependenciesKatharina Fey1-1/+1
2018-07-10Adding an example of how to register a user and adding new metadataKatharina Fey2-11/+87
vault endpoints functions
2018-07-10Adding the http ability to register/login and managing metadataKatharina Fey1-0/+25
2018-07-09Restoring the API handlers again, making it all work with the newKatharina Fey3-301/+244
Error system (all stubs for now)
2018-07-09Refactoring the error modules to now contain sub-error typesKatharina Fey3-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
2018-07-03Removing generics from error typesKatharina Fey2-6/+21
2018-07-02Throwing stuff against wallsKatharina Fey5-296/+324
2018-07-02This doesn't workKatharina Fey4-49/+39
2018-07-02Big code change & refactoring commitKatharina Fey1-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 :(
2018-07-01Refactoring models module, adding more inputsKatharina Fey5-19/+94
2018-06-30Fleshing out REST API fully and adding function stubsKatharina Fey3-27/+130
2018-06-30Ironing out some problems with the ApiState serialisationKatharina Fey1-15/+3
2018-06-30Adding more utility functions to a bunch of placesKatharina Fey1-4/+19
Integrating the userstore into the http crate
2018-06-22Fixing a bunch of syntax errors in the codeKatharina Fey4-8/+7
2018-06-22Bumping all dependenciesKatharina Fey3-1/+16
2018-06-13Bumping version numbers collectivelyKatharina Fey1-2/+2
2018-06-13Refactoring http API and making "not working" routes return a more ↵Katharina Fey4-14/+47
descriptive json
2018-06-12Working on the http layer, adding 'create' routeKatharina Fey4-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 😅
2018-06-12Starting work on lockchain-http scope filesKatharina Fey3-15/+90
2018-06-12Adding /api and /vault endpoints as first working routes ✨Katharina Fey3-5/+48
2018-06-12Bumping lockchain-core versionsKatharina Fey1-1/+1
2018-06-10Bumping other crate versionsKatharina Fey1-1/+1
2018-06-10Removing User & Login traits from core, adding a metadata store to take ↵Katharina Fey3-2/+16
their place
2018-06-10Adding a version prefix to all API routesKatharina Fey1-13/+14
2018-06-10Fixing documentation formatting :)Katharina Fey1-11/+11
2018-06-10Adding documentation for the REST API (to be)Katharina Fey1-1/+71
2018-06-09Bumping version numbersKatharina Fey1-1/+1
2018-06-09Tweaking the documentation for lockchain-httpKatharina Fey2-18/+18
2018-06-09Bumping and updating crate versionsKatharina Fey1-2/+2
2018-06-09Updating http documentationKatharina Fey1-22/+40
2018-06-09Tweaking the lockchain-http API, adding some constraints on vault traitsKatharina Fey3-52/+60
2018-06-09Working on lockchain integrationKatharina Fey4-7/+13
2018-06-09Refactoring http libraryKatharina Fey2-6/+15
2018-06-07Patch release (cargo release is broken!)Katharina Fey1-1/+1
2018-06-07Adding more documentationKatharina Fey2-6/+19
2018-06-07Starting work on the lockchain-http interface libraryKatharina Fey6-117/+115
2018-06-07A bunch of code changesKatharina Fey5-37/+144
2018-05-13Starting work on http crateKatharina Sabel3-0/+4
2018-05-11Fixing the manifest filesKatharina Sabel1-1/+1
2018-05-11Adjusting version numbers across the ecosystem to bring them all to the same ↵Katharina Sabel1-1/+1
level
2018-05-08Changing the way that vault traits workKatharina Fey1-1/+15
2018-05-08More crate metadata for crates ioKatharina Fey1-0/+9
2018-05-08Adding dependencies to http crate and publishing itKatharina Fey3-8/+21
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-26 19:54:39 +0000