How to install and configure a Docker container app as a site in ISPConfig

Hi. Thank you for your excellent work.
Running: ISPConfig 3.3
I have a few websites running in/under an ISPConfig installation.
I would like to add a website to my ISPConfig instance that will be an open source webapp. The webapp is provided as a Docker image/container (apologies—I am uncertain of the correct terminology at the moment). The app is Plane.
Naturally, I'll need HTTPS.

Here are a couple of links in case helpful:
https://plane.so
https://developers.plane.so/self-hosting/methods/docker-compose#install-community-edition

How might I go about making this work? I tried looking at some posts here that seem to be related to the topic, but they go over my head and I'm not even certain if they address what I'm looking for or not. I also attempted doing it on my own on a test server, but didn't really know what I was doing—it didn't work.

Thank you.

 

Very grateful for the overview! Thank you. And thank you for mentioning a possible port number to use.

Your Step 1):
Would you have suggestions on the values I might assign to these environmental variables I am supposed to define for the webapp? (This is a snippet from the Plane documentation. )

• LISTEN_HTTP_PORT: This is set to 80 by default. Make sure the port you choose to use is not preoccupied. For example, LISTEN_HTTP_PORT=8080
• LISTEN_HTTPS_PORT: This is set to 443 by default. Make sure the port you choose to use is not preoccupied. For example, LISTEN_HTTPS_PORT=4430
• WEB_URL: This is set to http://localhost by default. Change this to the FQDN you plan to use along with LISTEN_HTTP_PORT. For example, https://plane.example.com:8080 or http://[IP-ADDRESS]:8080.
• CORS_ALLOWED_ORIGINS: This is set to http://localhost by default. Change this to the FQDN you plan to use along with LISTEN_HTTP_PORT. For example, https://plane.example.com:8080 or http://[IP-ADDRESS]:8080.

I know you suggested as a possible port something like 8082, but if that gets assigned to LISTEN_HTTP_PORT, then what do I do with LISTEN_HTTPS_PORT? Likewise, should the WEB_URL be my real domain name that I have set up in ISPConfig for this site? Or? Apologies, these details aren't something I am familiar with.

Your Step 2):
I think I'm good on following that step.

Your Step 3):
(I use Apache.) May I request details on this part please? I figure this Step needs to work in harmony with the settings in Step 1, but the subject of proxies, etc aren't something I have a strong understanding of.

Again, thank you.

 

I do not have it working properly yet.
This is an update post on the configuration I have at the moment (that is not fully working).

In the plane webapp plane.env file, I have:

Code:

LISTEN_HTTP_PORT=8082
LISTEN_HTTPS_PORT=
WEB_URL=http://localhost:8082
CORS_ALLOWED_ORIGINS=http://localhost:8082
API_BASE_URL=http://api:8000

And in ISPConfig, I have the following settings:




This configuration seems to almost work. The title bar text (the webapp title) loads in the browser, but I get only a blank, white page in the browser. With the following in the browser console:


I feel like this must be related in some way to the "proxy" configuration perhaps not being exactly right. But my knowledge in this area is pretty weak at present.

Any thoughts or suggestions?

Thank you!

 

Update in my ongoing efforts:
Still not having success.
In the plane webapp plane.env file, I NOW have:

Code:

LISTEN_HTTP_PORT=8082
LISTEN_HTTPS_PORT=8083
WEB_URL=http://localhost:8082
CORS_ALLOWED_ORIGINS=http://localhost:8082
API_BASE_URL=http://api:8000
SITE_ADDRESS=https://test04.[domain].net/

According to "a find" on the Internet, the "SITE_ADDRESS" variable in the plane.env file must be "set to the domain name the users will use to access Plane (e.g., https://plane.yourdomain.com). This ensures that generated links and redirects work correctly." Thus, the adjustment I posted here.

But this results in the address in the browser address bar being changed to "localhost".