Software Heritage storage manager
Project description
swh-storage
Abstraction layer over the archive, allowing to access all stored source code artifacts as well as their metadata.
See the documentation for more details.
Quick start
Dependencies
Python tests for this module include tests that cannot be run without a local Postgresql database, so you need the Postgresql server executable on your machine (no need to have a running Postgresql server). They also expect a cassandra server.
Debian-like host
$ sudo apt install libpq-dev postgresql-11 cassandra
Non Debian-like host
The tests expects /usr/sbin/cassandra to exist.
Optionally, you can avoid running the cassandra tests.
(swh) :~/swh-storage$ tox -- -m 'not cassandra'
Installation
It is strongly recommended to use a virtualenv. In the following, we
consider you work in a virtualenv named swh. See the
developer setup guide
for a more details on how to setup a working environment.
You can install the package directly from pypi:
(swh) :~$ pip install swh.storage
[...]
Or from sources:
(swh) :~$ git clone https://forge.softwareheritage.org/source/swh-storage.git
[...]
(swh) :~$ cd swh-storage
(swh) :~/swh-storage$ pip install .
[...]
Then you can check it's properly installed:
(swh) :~$ swh storage --help
Usage: swh storage [OPTIONS] COMMAND [ARGS]...
Software Heritage Storage tools.
Options:
-h, --help Show this message and exit.
Commands:
rpc-serve Software Heritage Storage RPC server.
Tests
The best way of running Python tests for this module is to use tox.
(swh) :~$ pip install tox
tox
From the sources directory, simply use tox:
(swh) :~/swh-storage$ tox
[...]
========= 315 passed, 6 skipped, 15 warnings in 40.86 seconds ==========
_______________________________ summary ________________________________
flake8: commands succeeded
py3: commands succeeded
congratulations :)
Development
The storage server can be locally started. It requires a configuration file and a running Postgresql database.
Sample configuration
A typical configuration storage.yml file is:
storage:
cls: local
args:
db: "dbname=softwareheritage-dev user=<user> password=<pwd>"
objstorage:
cls: pathslicing
args:
root: /tmp/swh-storage/
slicing: 0:2/2:4/4:6
which means, this uses:
-
a local storage instance whose db connection is to
softwareheritage-devlocal instance, -
the objstorage uses a local objstorage instance whose:
-
rootpath is /tmp/swh-storage, -
slicing scheme is
0:2/2:4/4:6. This means that the identifier of the content (sha1) which will be stored on disk at first level with the first 2 hex characters, the second level with the next 2 hex characters and the third level with the next 2 hex characters. And finally the complete hash file holding the raw content. For example: 00062f8bd330715c4f819373653d97b3cd34394c will be stored at 00/06/2f/00062f8bd330715c4f819373653d97b3cd34394c
-
Note that the root path should exist on disk before starting the server.
Starting the storage server
If the python package has been properly installed (e.g. in a virtual env), you should be able to use the command:
(swh) :~/swh-storage$ swh storage rpc-serve storage.yml
This runs a local swh-storage api at 5002 port.
(swh) :~/swh-storage$ curl http://127.0.0.1:5002
<html>
<head><title>Software Heritage storage server</title></head>
<body>
<p>You have reached the
<a href="https://www.softwareheritage.org/">Software Heritage</a>
storage server.<br />
See its
<a href="https://docs.softwareheritage.org/devel/swh-storage/">documentation
and API</a> for more information</p>
And then what?
In your upper layer (loader-git, loader-svn, etc...), you can define a remote storage with this snippet of yaml configuration.
storage:
cls: remote
args:
url: http://localhost:5002/
You could directly define a local storage with the following snippet:
storage:
cls: local
args:
db: service=swh-dev
objstorage:
cls: pathslicing
args:
root: /home/storage/swh-storage/
slicing: 0:2/2:4/4:6
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file swh.storage-0.10.1.tar.gz.
File metadata
- Download URL: swh.storage-0.10.1.tar.gz
- Upload date:
- Size: 246.9 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.1.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.7.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
040372414dcd65a2c142003724a4421759fa5c3ee1f627aea92c936bdedc4f88
|
|
| MD5 |
27157ab8ffe450c2d592ad3aaf1a9feb
|
|
| BLAKE2b-256 |
5e96723cf6f277b4cd59bbf2e8e68846809b973e8ce00bc3295b3eb293d9d2ce
|
File details
Details for the file swh.storage-0.10.1-py3-none-any.whl.
File metadata
- Download URL: swh.storage-0.10.1-py3-none-any.whl
- Upload date:
- Size: 206.4 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.1.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.7.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
3fc4adcccfb2acdb9d73412bb8890082a408eb629adca092d376bea45f848223
|
|
| MD5 |
0bf7db5c99611b3de199f7aeb244eea6
|
|
| BLAKE2b-256 |
82e054fc391f78688065f04cebe26a9f605f3612b732ea927a91c54e982f9b92
|
