Most of the examples for making Docker images for the Container engine show connecting to the apps web server by navigating to a specific port. Is it possible to use the package manifest file to connect this to the ctrlX Reverse Proxy? Or is this not permitted through the Container Engine App?
Use Docker image with ctrlX OS reverse proxy?
Best reply by nickH
Update @StephenO
We just tested it and it works fine :)
Here a example docker-compose file:
version: '3.7'
services:
brc-web:
container_name: "hello-web" #unique container_name
image: ${IMAGE_NAME}:${IMAGE_TAG}
ports:
- "127.0.0.1:8188:8188"
stdin_open: false
tty: false
restart: always
volumes:
- brc-web-data:/data
volumes:
brc-web-data:Here my package-manifest.json file:
{
"$schema": "https://json-schema.boschrexroth.com/ctrlx-automation/ctrlx-core/apps/package-manifest/package-manifest.v1.1.schema.json",
"version": "1.0.0",
"id": "hello-web",
"menus": {
"sidebar": [
{
"id": "hello-web.dashboard",
"title": "Hello Web",
"icon": "bosch-ic-worldwideweb",
"target": "_blank",
"link": "/hello-web",
"permissions": []
}
],
"overview": [
{
"id": "hello-web.dashboard",
"title": "Hello Web",
"icon": "bosch-ic-worldwideweb",
"target": "_blank",
"link": "/hello-web",
"permissions": []
}
]
},
"services": {
"proxyMapping": [
{
"name": "docker-hello.web",
"url": "/hello-web",
"binding": ":8188"
}
]
}
}Best regards,
Nick
2 replies