Fix broken links and standardize exercise naming#651
Open
mayasrl wants to merge 1 commit intoglobocom:masterfrom
Open
Fix broken links and standardize exercise naming#651mayasrl wants to merge 1 commit intoglobocom:masterfrom
mayasrl wants to merge 1 commit intoglobocom:masterfrom
Conversation
- 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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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)