Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Labs: GitHub-177: Randomly generate log file's name to enhance log file's security #311

Closed
wants to merge 12 commits into from

Conversation

vishalkakadiya
Copy link
Contributor

@vishalkakadiya vishalkakadiya commented Oct 3, 2023

Nginx-Helper generates a predictable log file on a predefined path, so we are generating the file name randomly so it will be not detected by anyone else then the site Admin.

Ref: https://github.com/rtCamp/labs/issues/177

@vishalkakadiya vishalkakadiya changed the base branch from master to develop October 3, 2023 08:17
@nitun nitun requested a review from gagan0123 October 3, 2023 08:47
@vishalkakadiya vishalkakadiya changed the title Update log file path from uploads to web-root Labs: GitHub-177: Update log file's name to enhance log file's security Jan 10, 2024
@vishalkakadiya vishalkakadiya changed the title Labs: GitHub-177: Update log file's name to enhance log file's security Labs: GitHub-177: Randomly generate log file's name to enhance log file's security Jan 10, 2024
@gagan0123
Copy link
Member

@vishalkakadiya

Can you check why Playwright tests are failing

@vishalkakadiya
Copy link
Contributor Author

@pavanpatil1 Can you help here to fix these errors or guide me the next steps as we discussed in the Slack. Thanks!

CC @gagan0123

@vishalkakadiya
Copy link
Contributor Author

@gagan0123 The tests are fixed and passed now in the CI as well as in the local. Can you review the PR now, thanks! 🙂

CI: https://github.com/rtCamp/nginx-helper/actions/runs/7484035307/job/20370229295?pr=311#step:6:4239

Local:

Screenshot 2024-01-11 at 9 46 24 AM

@vishalkakadiya
Copy link
Contributor Author

Closing this PR as opened the new PR as discussed with the team.

#316

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.

3 participants