aboutcode-org / aboutcode-org/vulnerablecode

Enable Hot Reloading in Docker Container

Open
#1,771 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
702
Forks
328
Avg merge
3d 8h
Merged PRs (30d)
3

Description

"_Hot Reloading Not Working in Docker Container_" Live code updates inside the Docker container are not taking effect as expected. Currently, hot reloading requires a full container rebuild using ` docker compose up --build ` for changes to be reflected, which slows down the development process.

### Solution: How to Enable Hot Reloading?

1. Use Bind Mounts Modify docker-compose.yml to mount the code into the container:

```
services:
vulnerablecode:
volumes:
- .:/app # Syncs local changes with the container
```

2. Enable Gunicorn Auto-Reload Update the Gunicorn command to include the `--reload ` flag , allowing automatic reloading when code changes:

```
command:
gunicorn --reload vulnerablecode.wsgi:application -b :8000 --timeout 600 --workers 8
```
This setup allows the dockerized application to reflect the changes automatically when code changes are detected.

**How to Test ?**
> 1.Modify the code (Python files or static UI elements).
> 2. Check the container logs for updates:
``` sh docker compose logs -f vulnerablecode ```
> 3. Refresh the UI in the browser.
> 4. Verify the changes without rebuilding the container.

**Expected Outcome:**

- Code modifications should trigger an automatic reload inside the container.
- No need to manually rebuild the container after every change.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.