summaryrefslogtreecommitdiff
path: root/src/leap/soledad/server
AgeCommit message (Collapse)Author
2017-07-21[refactor] creates a common.blobs with preambleVictor Shyba
Refactor suggested from !105 review.
2017-07-18[feat] use MX as default namepace for incoming blobsdrebs
2017-07-18[style] fixes from reviewVictor Shyba
Updates IBlobsBackend with list_blobs order_by parameter and add a elif clause to order_by checking, raising if the ordering parameter isn't supported.
2017-07-18[feature] add namespace support for BlobsManagerVictor Shyba
'namespace' argument is supported by backend but not yet exposed on API for clients. Since IncomingBox makes heavy usage of it, this commit exposes the argument as a query string for clients to use it.
2017-07-18[feature] remote list sorting by dateVictor Shyba
Listing by date is useful for listing newest/oldest documents on blobs storage and should be used for listing new IncomingMessages as described on specification. -- Resolves: #8879
2017-07-18[feature] add blobs as a incoming api backendVictor Shyba
We started with CouchDB due legacy system relying on it. This commit adds the possibility of adding blobs as a IncomingAPI backend if blobs is enabled on config file. -- Resolves: #8868
2017-07-18[feature] add blobs as a incoming api backendVictor Shyba
We started with CouchDB due legacy system relying on it. This commit adds the possibility of adding blobs as a IncomingAPI backend if blobs is enabled on config file. -- Resolves: #8868
2017-07-02[feature] namespace capability to BlobsBackendVictor Shyba
Adds an extra parameter called "namespace" on the backend interface and on FileSystemBlobsBackend. This parameter overrides default id partitioning and uses a separate folder for a custom namespace. -- Resolves: #8889
2017-07-02[bug] fix file path from repo unifyVictor Shyba
2017-07-02[feature] direct /incoming requests to IncomingResourceVictor Shyba
Adds the routing code for exposing /incoming from SoledadResource. - Related: #8827
2017-06-24[bug] fix package __version__ attributedrebs
2017-06-24[pkg] unify client and server into a single python packagedrebs
We have been discussing about this merge for a while. Its main goal is to simplify things: code navigation, but also packaging. The rationale is that the code is more cohesive in this way, and there's only one source package to install. Dependencies that are only for the server or the client will not be installed by default, and they are expected to be provided by the environment. There are setuptools extras defined for the client and the server. Debianization is still expected to split the single source package into 3 binaries. Another avantage is that the documentation can now install a single package with a single step, and therefore include the docstrings into the generated docs. - Resolves: #8896