How to configure a context path?

[Thijs Borst]

I have an issue configuring a context path. Is this even possible? I can't find how to do this. I want to run the application under /dashboard instead of the root.

[Kutsal Berberoglu]

Any resolution for this? We're trying to do something similar; i.e. run a bunch of atlasboard instances for a bunch of different types of dashboards and would like to be able to provide a well-known entrance to the boards via something like http://atlasboard.internal/boards/XYZ which then proxies to http://localhost:PORT_FOR_XYZ/

Without a context path, socket.io stuff doesn't work since its client uses a relative path (/socket-io) to ping back...

[Eric Hirlemann]

@kutsal Wouldn't that be rather the job of a proxy service as httpd? We have such a configuration where {{atlasboard.internal.our.domain}} is visible to users while it proxies to {{physical.machine.onthecloud:port}}

[Kutsal Berberoglu]

@hirle true, but because of the way socket.io client is used, i.e. it's running on client side in the browser, it's tough to write a server-side rewrite rule to send clients back to the atlasboard instance running their dashboards. Our use case(s) of:

http://atlasboard.internal/board1/foo -> http://localhost:PORT_FOR_board1/foo http://atlasboard.internal/board2/bar -> http://localhost:PORT_FOR_board2/bar etc...

breaks because of the /socket-io/?EIO=3&transport=polling&t=XYZ calls the clients make. (note the / at the beginning)

[Craig Guest]

@kutsal, in lieu of atlassian adding some form of server base uri configuration I ended up adding a rather nasty sub_filter in nginx:

sub_filter_types application/javascript text/css;
sub_filter 'widgets/' '<name>/widgets/';
sub_filter '../../fonts/' '/<name>/fonts/';
sub_filter 'path||"/socket.io"' 'path||"/<name>/socket.io"';

It works, but it's not pretty.