aboutsummaryrefslogtreecommitdiff
path: root/lockchain-files (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Updating license in crate metadataHEADmasterKatharina Fey2019-04-231-2/+5
|
* Running rustfmtKatharina Fey2019-04-226-13/+12
|
* Updating crates to 2018 edition (#9)Katharina2019-04-227-50/+50
| | | | | | * Updating main README * Updating lock file * Updating crate ecosystem to Rust 2018 edition
* Fixing documentation test casesKatharina Fey2018-09-161-1/+1
|
* Assorted changesKatharina Fey2018-09-167-63/+81
|
* Only relying on the `UserStore` `AutoEncoder` impl for serialisationKatharina Fey2018-09-163-2/+20
|
* Adding primitive file utilitiesKatharina Fey2018-09-164-49/+87
|
* A large batch of refactoring in FileVaultKatharina Fey2018-09-155-84/+117
| | | | | | | | | | | | | | | | | | | | | | | | | Okay what am I doing here? If you're reading this in the future, it probably means I made some bad decisions. First: I'm sorry. Secondly: let me explain why I did what I did... Until this point `FileVault` has been a very transparent structure. It didn't really interact with the data much, basically solving all fs operations with streamed iterators and making sure stuff was done correctly, but not adding any depth on top of that. This needed to change... This isn't quite done and most of the code just breaks here ;) But the idea is to have `FileVault` be an intelligent wrapper around the filesystem. That means that not only does it cache certain operations for speed, it also keeps a selective index of files that exist. So for example, `Headers` were added here, that are always kept in sync with the FS. But only certain Records are stored (not only for security but also size consearns). After this refactoring is done (I shall write another long commit) the FileVault will act more as it's own type than just a simple, linear `Vault<T>` implementation.
* Updating a bunch crates and generating keysKatharina Fey2018-09-152-5/+12
|
* Using the new generators to create filevaultKatharina Fey2018-09-154-45/+57
|
* Restructuring internal layout and working on Generator intergrationKatharina Fey2018-09-153-54/+21
|
* A lot of refactoring in lockchain-filesKatharina Fey2018-09-157-66/+119
|
* Starting work on the lockchain-core --> lockchain-files userstore mapperKatharina Fey2018-09-082-2/+21
|
* Assorted code fixesKatharina Fey2018-09-082-17/+26
|
* Various smol changes around the new Generator APIKatharina Fey2018-09-062-22/+20
|
* Removing deprecated `UserStore` and `KeyStore` into new `users::UserStore`Katharina Fey2018-09-061-7/+25
| | | | and fixing all resulting code issues
* Refactoring the vault trait to consume a generator structKatharina Fey2018-09-061-1/+3
|
* Now writing the config after vault scaffolding – woops. Making a small ↵Katharina Fey2018-09-043-45/+61
| | | | example work
* Cleaning up the core a bit. Adding better (any) config handling to filesKatharina Fey2018-09-047-81/+278
|
* Generally refactoring some code (this is a bad commit message)Katharina Fey2018-09-031-2/+16
|
* More refactoring and trying to get keystores to work properlyKatharina Fey2018-08-061-1/+1
|
* (cargo-release) start next development iteration 0.9.1-alpha.0Katharina Fey2018-07-121-1/+1
|
* (cargo-release) version 0.9.0Katharina Fey2018-07-121-1/+1
|
* See previous commit message...Katharina Fey2018-07-121-1/+1
|
* (cargo-release) version 0.8.0Katharina Fey2018-07-121-1/+1
|
* Changing a bunch of version numbers around. This is really not a good solutionKatharina Fey2018-07-121-1/+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 a new keystore to lockchain-core::crypto, composing a userstoreKatharina Fey2018-07-122-9/+11
| | | | | from two metadomains now (users, registry) to allow for a better user registry pipeline. Tweaking examples to make all this work and generally cleaning up code
* Adding an example of how to register a user and adding new metadataKatharina Fey2018-07-103-8/+19
| | | | vault endpoints functions
* Adding more utility functions to a bunch of placesKatharina Fey2018-06-301-2/+4
| | | | Integrating the userstore into the http crate
* Implementing `meta_push_domain` for files backendKatharina Fey2018-06-301-0/+5
|
* Bumping all dependenciesKatharina Fey2018-06-221-1/+11
|
* Bumping version numbers collectivelyKatharina Fey2018-06-131-2/+2
|
* Adding /api and /vault endpoints as first working routes ✨Katharina Fey2018-06-121-3/+11
|
* Bumping lockchain-core versionsKatharina Fey2018-06-122-3/+2
|
* Fixing an issue in the metadomain insert function and fixing some file sync ↵Katharina Fey2018-06-122-2/+17
| | | | issues
* Another small tweak to the vault APi – I'll get it right at some pointKatharina Fey2018-06-111-3/+3
|
* Fixing a bug in the vault API, implementing more fileKatharina Fey2018-06-113-34/+55
|
* Adding a list type to PayloadKatharina Fey2018-06-102-10/+29
|
* Bumping other crate versionsKatharina Fey2018-06-101-1/+1
|
* Bumping and updating crate versionsKatharina Fey2018-06-091-2/+2
|
* Tweaking the lockchain-http API, adding some constraints on vault traitsKatharina Fey2018-06-091-1/+1
|
* Starting work on http crateKatharina Sabel2018-05-132-9/+52
|
* Fixing the manifest filesKatharina Sabel2018-05-111-2/+2
|
* Adjusting version numbers across the ecosystem to bring them all to the same ↵Katharina Sabel2018-05-111-1/+1
| | | | level
* Implementing some backend storage functions for filevaultKatharina Sabel2018-05-103-23/+62
|
* Getting an initial API for lockchain-files readyKatharina Sabel2018-05-101-1/+1
|
* Finishing up crypto releaseKatharina Sabel2018-05-101-1/+1
|
* HmmKatharina Sabel2018-05-101-1/+1
|
* Updating README, breaking compilationKatharina Sabel2018-05-102-5/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-02 06:12:15 +0000