Changeset View
Changeset View
Standalone View
Standalone View
docker/README.rst
Show First 20 Lines • Show All 383 Lines • ▼ Show 20 Lines | swh-scheduler-runner service):: | ||||
swh-scheduler-runner_1 | raise self.NotRegistered(key) | swh-scheduler-runner_1 | raise self.NotRegistered(key) | ||||
swh-scheduler-runner_1 | celery.exceptions.NotRegistered: 'swh.lister.debian.tasks.DebianListerTask' | swh-scheduler-runner_1 | celery.exceptions.NotRegistered: 'swh.lister.debian.tasks.DebianListerTask' | ||||
Using docker setup development and integration testing | Using docker setup development and integration testing | ||||
------------------------------------------------------ | ------------------------------------------------------ | ||||
If you hack the code of one or more archive components with a virtual | If you hack the code of one or more archive components with a virtual | ||||
env based setup as described in the | env based setup as described in the | ||||
[[https://docs.softwareheritage.org/devel/developer-setup.html|developer | `developer setup guide <https://docs.softwareheritage.org/devel/developer-setup.html>`__, you may want to test your modifications in a working | ||||
setup guide]], you may want to test your modifications in a working | |||||
Software Heritage instance. The simplest way to achieve this is to use | Software Heritage instance. The simplest way to achieve this is to use | ||||
this docker-based environment. | this docker-based environment. | ||||
If you haven’t followed the | If you haven’t followed the | ||||
[[https://docs.softwareheritage.org/devel/developer-setup.html|developer | `developer setup guide <https://docs.softwareheritage.org/devel/developer-setup.html>`__, you must clone the the [swh-environment] repo in your | ||||
setup guide]], you must clone the the [swh-environment] repo in your | |||||
``swh-environment`` directory:: | ``swh-environment`` directory:: | ||||
~/swh-environment$ git clone https://forge.softwareheritage.org/source/swh-environment.git . | ~/swh-environment$ git clone https://forge.softwareheritage.org/source/swh-environment.git . | ||||
Note the ``.`` at the end of this command: we want the git repository to | Note the ``.`` at the end of this command: we want the git repository to | ||||
be cloned directly in the ``~/swh-environment`` directory, not in a sub | be cloned directly in the ``~/swh-environment`` directory, not in a sub | ||||
directory. Also note that if you haven’t done it yet and you want to | directory. Also note that if you haven’t done it yet and you want to | ||||
hack the source code of one or more Software Heritage packages, you | hack the source code of one or more Software Heritage packages, you | ||||
really should read the | really should read the | ||||
[[https://docs.softwareheritage.org/devel/developer-setup.html|developer | `developer setup guide <https://docs.softwareheritage.org/devel/developer-setup.html>`__. | ||||
setup guide]]. | |||||
From there, we will checkout or update all the swh packages:: | From there, we will checkout or update all the swh packages:: | ||||
~/swh-environment$ ./bin/update | ~/swh-environment$ ./bin/update | ||||
Install a swh package from sources in a container | Install a swh package from sources in a container | ||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||||
▲ Show 20 Lines • Show All 453 Lines • Show Last 20 Lines |