You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
worker:
build: .
# Ensure that potential db migrations run first by waiting until "web" is up
command: wait-for-it --strict --timeout=120 web:8000 -- sh -c "
./manage.py rqworker --worker-class scancodeio.worker.ScanCodeIOWorker
--queue-class scancodeio.worker.ScanCodeIOQueue
--verbosity 1"
Lastly the clamav configuration is not present (image and volumes)
Hey @AlexBaranowski , I'm exited to address this issue, i've already cloned the repository on my system. please assign me this issue, i'm learning how the offline installation is working, also let which specific files should i look into? Thank you!
Thanks for getting back to me! I appreciate the details in the issue description. The fixes seem straightforward:
Correcting image names in docker-compose-offline.yml.
Unifying the worker command between the two compose files.
Adding ClamAV to the offline setup.
Ensuring Makefile exports the ClamAV image.
Reviewing and updating documentation if needed.
I'll go ahead and start working on these changes and will create a PR once done. Let me know if you have any additional pointers or things I should be aware of.
Current offline installation require update to config files and probably documentation. The following should be fixed:
docker-compose-offline.yml
Exported image is named scancodeio-web
Exported image is named scancodeio-worker
Also the starting command should be unified:
The docker-compose.yml vs docker-compose-offline.yml
Lastly the clamav configuration is not present (image and volumes)
With
vimdiff
the configurations should probably not match only onimage: XXX
andbuild: .
Makefile
Makefile should be updated so the
docker-images:
target would also export the clamav image.Documentation
Lastly documentation should be revisited to check if it's up to date.
Best,
Alex
The text was updated successfully, but these errors were encountered: