Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
Closes #8850.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Resolves: #8804
|
|
|
|
The image location needs to be changed to the new location and
the docker.io package needs to be available in the image to
build it
|
|
When the testing/docker directory is changed, the `build_docker_image`
CI job is triggered to build the docker image and push it to the
soledad container registry.
This is part of an effort to move all the docker images into their own
project's container registry, and to build/provide them
automatically (see leap/platform#8755).
This is accomplished by the following:
added the necessary overlay DOCKER_DRIVER variable to .gitlab-ci.yml
added a build_docker_image job with docker:dind service enabled
enabled container registry in soledad project
added LEAP_CODE_O_MATIC_PRIVATE_TOKEN to project
moved docker image from scripts:docker/soledad to soledad:testing/docker
docker push gitlab-buildpackage:soledad to soledad container registry
removed gitlab-buildpackage:soledad image and scripts/docker/soledad
changed image in .gitlab-ci.yml to use new location
Note: until https://gitlab.com/gitlab-org/gitlab-ce/issues/19813 is
resolved, we have to use this method.
|
|
- rename add_tag method
- reorder blob interface methods for clarity
- use mkdir_p from leap.common
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add a DELETE method for blobs server and integrate it into client's
BlobManager.
- Resolves: #8846
|
|
- Related: #8846
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Check if user and blob_id are valid strings, then check if the resulting
path is a subdirectory of blobs configured path.
- Related: #8800
|
|
- Related: #8812
|
|
BlobManager tests covers them indirectly, but testing them directly may
help locating source of bugs.
- Related: #8812
|
|
- Related: #8812
|
|
- Related: #8812
|
|
We can't let the local DB try an isertion before making sure doc isn't
already there.
- Resolves: #8845
|
|
|
|
|
|
|
|
|
|
_validate will check if user_id and blob_id are letter, numbers, dashes
and underscores. It is called on render_GET and render_POST, validating
incoming arguments before handling on backend.
- Resolves: #8832
|
|
This makes process communication async during quota measurement, as
specified on #8832
- Related: #8832
|
|
During a meeting with pixelated we were asked to ensure that the u1db
revision system was working for the shared database. This commit adds a
test to make sure that documents in the shared database can be updated
successfully if the include the correct revision, but will fail if the
include the incorrect revision.
Resolves: #8842.
|