Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose work web UI inside a path prefix #43

Open
vin-rmdn opened this issue Sep 23, 2024 · 0 comments · May be fixed by #44
Open

Expose work web UI inside a path prefix #43

vin-rmdn opened this issue Sep 23, 2024 · 0 comments · May be fixed by #44

Comments

@vin-rmdn
Copy link

Hi Gojek folks, thanks for the effort in maintaining gocraft / gojek/work!

I have a use case, where we plan to attach the monitoring UI inside a prefix of an existing server. I see that inside webui folder we only expose a constructor for a server – is it possible that we expose handler as well, for easy plug-in with other server (e.g., Mux)?

The server will end up with this API structure:

  • /ping : containing liveness check
  • /{anything else} : contains business logic for our server
  • /monitoring/* : will contain the gojek/work server UI

This way, we can host the worker monitoring UI inside the same server we use for our business logic as well. This is necessary for us because, on our infrastructure where we have server and worker, we only expose port 8080 of the server, making it impossible for us to host the worker monitoring UI from the worker itself, or on a different port of the server.

Better example will be like this: https://github.com/hibiken/asynqmon?tab=readme-ov-file#import-as-a-library

Thanks in advance folks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant