Issue with OpenRemote Custom Deployment - Connection Refused on Port 8080

Custom Deployment
1

Hi there,

I’m trying to run a custom deployment of OpenRemote following the steps mentioned in the Custom Deployment User Guide.

1- Set up the environment:

java --version
java 17.0.10 2024-01-16 LTS
Java™ SE Runtime Environment (build 17.0.10+11-LTS-240)
Java HotSpot™ 64-Bit Server VM (build 17.0.10+11-LTS-240, mixed mode, sharing)

yarn --version
1.22.22

docker --version
Docker version 24.0.2, build cb74dfc

docker-compose --version
Docker Compose version v2.18.1

2- Cloned the custom-project template repository and initialized the openRemote submodule.

3- Ran the command: docker-compose -f profile\dev-testing.yml up --build -d. The keycloak and postgres containers are up and healthy:

image
image1900×175 11.4 KB

4- Ran ./gradlew modelWatch, which executed successfully

5- Attempted to browse: http://localhost:9000/manager/ after running npm run serve -- --env config=..\..\..\..\deployment\manager\app from openremote/ui/app/manager.

However, the OpenRemote blank page showed up for a second, then redirected to: http://localhost:8080/auth/realms/master/protocol/openid-connect/auth?client_id=openremote&redirect_uri=http%3A%2F%2Flocalhost%3A9000%2Fmanager%2F&state=94827a09-ee18-490f-8e08-39ac8bb394b4&response_mode=fragment&response_type=code&scope=openid&nonce=da9df74b-bf70-484c-8268-60e41e7cef43

I received a “connection refused” error, as there is nothing running on port 8080.

Please help me figure out what I’m missing here.

2

What I believe is happening is that the system is expecting the manager to be running on port 8080, but there’s no mention of this requirement in the wiki.

My goal is to make some modifications to the UI components as per my needs.

3

First of all, welcome! :partying_face:

The dev-testing profile is meant for developers who work on either
the OpenRemote ‘backend’ that runs on port 8080 (we name it “the Manager”),
or the OpenRemote ‘frontend’ (we name it “the Manager UI”).
So, in this case you’ll run the Manager Java instance yourself, within your preferred IDE.

.
However, in your case, you might prefer;

The dev-ui profile is meant towards developing UI apps or components,
where the Manager ‘backend’ is ran in a docker container. So, you don’t need to run it yourself :wink:

Hope this helps!

4

Thank you for your reply, @martin.peeters

I managed to run it using the following steps:

  1. ./gradlew clean installDist
  2. docker build -t openremote/manager:latest ./manager/build/install/manager
  3. docker-compose -p openremote up -d

This created the manager image locally and ran the container from it. So, whether I change the UI or backend code, the updates will be reflected.