HAL console and reverse proxies

[Mike Douglass]

The HAL console is a valuable tool but sitting on port 9990/9993 is a problem. My customers (and I for that matter) are unwilling to open up those ports to the outside world.

My solution has been to configure haproxy to redirect the context /console and /management to the appropriate port on the server.This also only works if there is a single sub-domain for the server. E.g. I don't think I can do

myDomain.com/server1/console

but have to do

server1.myDomain.com/console

This seems to work and it's useful having the server specific domains for testing anyway (though see my previous message about deployments).

Can we either:

1. Add documentation showing exactly how to configure reverse proxies. I had to search around and then convert nginx solutions to haproxy. Or

2. Repackage HAL as a regular application with a context that we can map like any other context.

What got me particularly interested in HAL is a customer who hides behind a VPN that cuts off all access other than their systems so once on their vpn on my laptop I'm reduced to using my phone for web access. Being able to deploy (again see previous message)/download logs and restart servers without getting on their vpn is very useful.

 It's a valuable tool which ideally ought to just show up on the usual web ports - perhaps after configuring the contexts.

In the meantime I'd be happy to share my haproxy config - which I'm sure can be improved - and I might be able to dig out the articles for nginx and I think apache. 

[Harald Pehl]

I don't know if you know about HAL standalone mode [1]. You can start HAL as a standalone application (either as a native binary, docker image, or online) and connect to a running management interface. 

Maybe that's an alternative to your setup. 

[1] https://hal.github.io/documentation/get-started/#standalone-mode

[Michael Douglass]

I can look at that. The advantage of the wildfly install is that it's just another feature in galleon.

If HAL is essentially just a big SPA I guess I could look at wrapping it up myself.

What I think I'd like to be able to do is parameterise the script so that I can set the url of the management interface - e.g https://myhost.com/myhalmanagement which haproxy can map onto the actual url.

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/c0fef3ae-90ba-4fc0-9b2c-1cbaf88c88b7n%40googlegroups.com.

[Harald Pehl]

If you want to wrap up the console yourself, please use [1]. The JAR contains all necessary HTML, JS, and CSS artifacts and is used for the HAL standalone mode. 

[1] https://repo1.maven.org/maven2/org/jboss/hal/hal-console/3.6.4.Final/hal-console-3.6.4.Final-resources.jar