[Feat]: Dual issue and Feature opportunity: Incorporating known extension ports into Docker-Compose for streamline port proxy processes

[CtheCondor]

What is your suggestion?

Incorporate known ports used by extensions in docker-compose to better facilitate/streamline the proxy port process

Why do you want this feature?

I want to build a web accessible Personal Knowledge Resource using the VSCode extension dendron however the dendron local server does not appear to work on the web based on my current usage.

Are there any workarounds to get this functionality today?

I have not been able to get it to work however I would not be surprised if there is a workaround.

Are you interested in submitting a PR for this?

I do not have the programmatic experience to do so at this time.

My Setup

1. Stock coder/code-server image running on 8443
2. Nginx Proxy Manager running on same machine in the same bridged docker network 2a. A *.domain.com lets Encrypt Certificate 2c. A Single Proxy host connecting my pkm.domain.com to my pkm_container:8443 using the container:port syntax with standard https required flags and proxy settings based on NPM.

[jsjoeio]

Which part of Dendron doesn't work for you? I tested it locally and it seems to be working:

[CtheCondor]

What browser are you running your code-server implementation and are you accessing it via https using a local cert or reverse proxy or is it local via http?

When I access the extension stock; I am left with an error on the Tree and on the graph view for the extension as shown above

[jsjoeio]

Interesting...I'm use the PWA with Brave Browser, 4.9.1 and running locally on my macOS. Accessing via http but it's on the same machine so it's considered secure.

[code-asher]

Closing this out since if there are issues here, it seems likely to be with the extension.