Expose generated results via lightweight NGINX web server#13
Open
matiasAS wants to merge 8 commits intoolivierb46:mainfrom
Open
Expose generated results via lightweight NGINX web server#13matiasAS wants to merge 8 commits intoolivierb46:mainfrom
matiasAS wants to merge 8 commits intoolivierb46:mainfrom
Conversation
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
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.
Summary
This PR adds an optional, lightweight NGINX web server to expose the generated
results/directory over HTTP after the rule extraction process finishes.The existing behavior is preserved:
Once the Python process completes, NGINX starts and serves the generated files.
How it works
results/8080No changes were made to the core Python logic or data flow.
Usage