summaryrefslogtreecommitdiff
path: root/src/leap/soledad/server
AgeCommit message (Collapse)Author
2017-09-05[pkg] move server.tac to server src folderVictor Shyba
This way the file gets copied during package install. -- Related: #8867
2017-09-05[refactor] add localhost endpoint to server tacVictor Shyba
-- Related: #8867
2017-09-05[feature] add a local realm with file auth checkerVictor Shyba
-- Related: #8867
2017-09-05[feature] new config option for tokens auth fileVictor Shyba
-- Related: #8867
2017-08-31[feat] get config file name from environmentdrebs
For tests, we may want to configure the server with non-default options, and the easiest way to do this is by creating a configuration file in a temporary directory and passing the file name by means of an environment variable. This commit changes the server config file loading scheme to account for a variable called SOLEDAD_SERVER_CONFIG_FILE. If that variable is set, the configuration is read from the file pointed by it. Otherwise, /etc/soledad/soledad-server.conf is used.
2017-08-23[bug] revert setting of default config that enabled blobs prematurelyKali Kaneko
We do not want to enable blobs on any server that, by mistake, deploys from master or from a released version in the 0.10.x series. for testing it's more sensible to allow instantiating the server with a custom config file.
2017-08-23[bug] add missing DELETE permission for blobsdrebs
2017-08-23[test] use sensible server default config for testingdrebs
2017-08-23[bug] add slash to end of blobs listing url in mapperdrebs
2017-08-23[bug] use correct keyword argumentdrebs
2017-08-23[bug] use correct StringIO classdrebs
2017-08-11[bug] enforce namespace to default on serverVictor Shyba
This commit is complementary to the previous one. It adds a test for the reported bug (listing default namespace was listing others) and fixes it. -- Related: #8882
2017-08-11[feature] add path partitioning to namespacesVictor Shyba
All blobs were being stored in a single folder when using namespaces, this commits adds path partitioning as discussed on #8882, which should help with a large number of files (each folder will hold a smaller subset, allowing the use of better filesystem walk strategies). Also, the default empty namespace is now called 'default' to prevent it from listing other namespaces contents. So everything will always use namespaces, with the option to use it explicitly or just fall to the default one. -- Related: #8882
2017-08-11[refactor] add IIncomingBoxBackendVictor Shyba
IIncomingBoxBackend holds backend specific methods used for IncomingBox implementation. - Resolves: #8888
2017-08-03[bug] separate preamble from content on incoming resourceVictor Shyba
2017-08-03[bug] flag as PENDING during incoming creationVictor Shyba
Clients will query for blobs flagged PENDING so they can start processing. This commit adds flagging, but still in a hacky way as the backend requires the flags as a json string inside a request. A refactor to separate request handling from the backend itself will solve it in the near future. -- Related: #8874
2017-08-03[bug] make download namespace-awareVictor Shyba
2017-07-21[refactor] error handling and missing headersVictor Shyba
Improves error handling, add missing header to __init__.py and remove mkdirs from flags methods. This is a commit from code review on !117.
2017-07-21[refactor] fixes from reviewVictor Shyba
Improve test naming, creates a "count" method and filter flags files properly.
2017-07-21[feature] LIST blobs - filter by flagsVictor Shyba
filter_flag parameter can now be used to filter listing blobs by a specific flags. Eg: I can ask for blobs on incoming namespace flagged as pending. -- Resolves: #8913
2017-07-21[feature] add possibility to count on blob managerVictor Shyba
By using `only_count=True` parameter, instead of returning a full list, server just count the amount of blobs. -- Resolves: #8871
2017-07-21[feature] add get/set flagsVictor Shyba
IncomingBox spec has a flags feature for the processing flow of messages. This commit adds it using a .flags file. -- Resolves: #8869
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