Closed brenner-tobias closed 3 weeks ago
The changes involve modifications to multiple configuration files: .devcontainer.json
, cloudflared/config.yaml
, and several translation files. In .devcontainer.json
, the port mapping for the development container has been updated, and the structure has been reorganized to group extensions and settings under a new customizations
key. In cloudflared/config.yaml
, a new web interface entry for metrics has been added along with a new ports
section that defines TCP port mapping for the metrics interface. Additionally, new entries for the metrics web interface have been introduced in various translation files.
File | Change Summary |
---|---|
.devcontainer.json | Updated appPort from "81:81" to "36500:36500" . Moved extensions and settings under customizations.vscode . Preserved mounts . |
cloudflared/config.yaml | Added new webui entry for metrics URL. Introduced ports section for TCP port 36500 . |
cloudflared/translations/de.yaml | Added new entry 36500/tcp: Web-Interface für Metriken (36500/tcp) in the network section. |
cloudflared/translations/en.yaml | Added new entry 36500/tcp: Metrics Web Interface (36500/tcp) in the network section. |
cloudflared/translations/he.yaml | Added new entry 36500/tcp: ממשק אינטרנט למדדים (36500/tcp) in the network section. |
cloudflared/translations/nl.yaml | Added new entry 36500/tcp: Webinterface voor statistieken (36500/tcp) in the network section. |
sequenceDiagram
participant DevContainer
participant VSCode
participant Cloudflared
DevContainer->>VSCode: Configure appPort
VSCode-->>DevContainer: Update appPort to 36500
DevContainer->>VSCode: Move extensions and settings under customizations
VSCode-->>DevContainer: Confirm structure update
Cloudflared->>Metrics: Access metrics web interface
Metrics-->>Cloudflared: Display metrics on port 36500
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
There is one issue with the way I implemented it: Since I added the webui: http://[HOST]:[PORT:36500]/metrics
config, the link for the webui is visible in the add-on page. If you do not actively add the port though, clicking on the link loads a blank website about:blank#blocked
We do have three options:
I am leaning towards option 2, since this is a niche use case anyways, but I could also live with 3.
@elcajon what do you think?
I would also tend towards option two, as otherwise the question would arise as to whether you need to forward the port on your router in order to be able to use the add-on and the tunnel at all...
Proposed Changes
Expose Metrics Server Port and add WebUI URL in Configuration
Related Issues
725
Summary by CodeRabbit
New Features
Configuration Improvements