Skip to content

Conversation

@mayasrl
Copy link

@mayasrl mayasrl commented Oct 23, 2025

Fixes #588
Fixes #587

This solution refers to which of the apps?

Multiple apps - fixing documentation links and docker-compose naming across the repository.

What did you do to mitigate the vulnerability?

This isn't a vulnerability fix, just maintenance work on documentation and naming consistency:

  • Fixed 5 broken links in README files (main README and a few exercise READMEs)
  • Standardized naming in 12 docker-compose.yml files to match their OWASP categories
  • Renamed a Dockerfile and updated some environment variables to keep everything consistent

The issue was that some exercises had container names from wrong categories (like a5 in an a1 folder), which could confuse people navigating the repo.

Did you test your changes? What commands did you run?

Yeah, I checked all the links to make sure they work now and verified that the docker-compose files have the right naming pattern. No code logic changed, just organizational stuff.

Total: 18 files modified (4 READMEs + 14 config files)

- Fixed 5 broken links in README files (issue globocom#588)
- Standardized naming in 12 docker-compose.yml files (issue globocom#587)
- Updated container names, networks, and databases to match OWASP categories
- Renamed a1inj.Dockerfile to a3inj.Dockerfile in copy-n-paste
- Updated environment variables in saidajaula-monster app.py

Fixes globocom#588
Fixes globocom#587
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Check and update broken links Check and update exercise setups names

1 participant