Skip to content

Conversation

@Ra9huvansh
Copy link

This PR updates the reverse proxy flow diagram (PNG) to align with the
GraphQL access changes introduced in #1450.

The SVG hasn’t been updated yet due to the lack of an updated source. Other
documentation is left unchanged to keep the scope of this PR minimal.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 28, 2026

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • docs/img/REVERSE_PROXY/reverse_proxy_flow.png is excluded by !**/*.png

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review

Comment @coderabbitai help to get the list of available commands and usage tips.

@adamoutler
Copy link
Collaborator

#1450 was not created in this way. #1468 was implemented instead and will be merged shortly. There are now two workflows and the one in the picture is not required.

Default

flowchart LR
  B[Browser]

  subgraph NAC[NetAlertX Container]
    N[Nginx listening on port 20211]
    A[Service on port 20212]
    N -->|Proxy /server to localhost:20212| A
  end

  B -->|port 20211| N
  B -->|port 20212| A
Loading

With proxies

flowchart LR
  B[Browser] -->|HTTPS| S[Any Auth/SSL proxy]
  B --> G[Any API consumer<br> eg. Grafana]
  subgraph NAC[NetAlertX Container]
    N[Nginx listening on port 20211]
    N -->|Proxy /server to localhost:20212| A[Service on port 20212]
  end
  S -->|port 20211| NAC
  G -->|port 20212| NAC
Loading

@Ra9huvansh
Copy link
Author

Ra9huvansh commented Jan 29, 2026

Thanks for clarifying!

Got it. I was working based on #1450. If #1468 replaces that approach
and this diagram isn’t needed anymore, I’m happy to close the PR.

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.

2 participants