28 Mar 2024 |
helenemj | * and overriding in swh-environment is the way to take into account changes in local repositories, am I right? | 16:22:12 |
david | well technically you can put the docker/ repo anywhere (it's not necessary to have it inder swh-environment), but TL;DR, yes | 16:24:15 |
helenemj | ok :) | 16:24:47 |
david | if you want to start a service in docker using your local copy of the sources for a swh-xxx package, then you have to make it mounted in the container in /src/swh-xxx | 16:25:22 |
david | the entrypoint will detect this and pip install it on startup | 16:25:37 |
Lunar | see https://docs.softwareheritage.org/devel/getting-started/using-docker.html#install-a-swh-package-from-sources-in-a-container | 16:26:06 |
IRC Relay Bot | <swhbot> ^ Docker environment — Software Heritage documentation | 16:26:07 |
helenemj | Thanks! | 16:26:58 |
david | if you struggle too much we can take some time to pair on this | 16:27:35 |
helenemj | ah that might be necessary at some point 😊 thanks! For now I still have some questions that can help me go further | 16:28:53 |
helenemj | (if it is the place I can ask them?) | 16:29:02 |
david | sure | 16:29:53 |
helenemj | Is it different to run docker compose inside our outside the virtual env? I'm explaining myself, I was able to reach http://localhost:5080/ when it was in an outside folder, but now I get a 502 error, is it related? | 16:30:11 |
david | should not | 16:30:30 |
helenemj | * Is it different to run docker compose inside our outside the virtual env? I'm explaining myself, I was able to reach http://localhost:5080/ when it was in an outter folder, but now I get a 502 error, is it related? | 16:30:30 |
helenemj | * Is it different to run docker compose inside or outside the virtual env? I'm explaining myself, I was able to reach http://localhost:5080/ when it was in an outter folder, but now I get a 502 error, is it related? | 16:30:47 |
david | the venv you are in should have nothing to do with the compose session | 16:31:27 |
helenemj | ok! | 16:31:33 |
helenemj | l am double checking th overriding file, I might have made a mistake | 16:31:49 |
david | check the logs of the compose services (e.g. 'docker compose logs nginx' to see the logs of nginx, which is used as the border http router for the swh stack within the compose session) | 16:33:15 |
helenemj | ok just starting it again worked, sorry!! | 16:33:16 |
helenemj | In reply to @david:sdfa3.org check the logs of the compose services (e.g. 'docker compose logs nginx' to see the logs of nginx, which is used as the border http router for the swh stack within the compose session) good to know, thanks :) | 16:33:30 |
david | or 'docker compose logs swh-web' for the logs of the web frontend service | 16:33:45 |
david | etc | 16:33:46 |
Lunar | enjoy the heatwaves :) | 16:35:21 |
david | yep, better doing this during winter time | 16:35:51 |
ardumont | 😄 | 16:39:02 |
helenemj | 😆 | 16:39:10 |
IRC Relay Bot | <swhbot> News from swhdocsdevfailures: swh-docs » dev #6229 (broken since this build) <https://jenkins.softwareheritage.org/view/all/job/DDOC/job/dev/6229/> | 18:44:02 |
IRC Relay Bot | <swhbot> News from swhdocsdevfailures: swh-docs » dev #6230 (broken since build #6229) <https://jenkins.softwareheritage.org/view/all/job/DDOC/job/dev/6230/> | 20:44:15 |