Support URL rewrite for Temporal UI when instrumenting via server golang package
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 431
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 71
Description
Is your feature request related to a problem? Please describe.
Our usecase is very much similar to https://github.com/temporalio/ui/issues/911, with the difference that we plan to run the temporal server in a goroutine from inside a binary using the server package.
Describe the solution you'd like
The binary would run a web server. We should like a subpath of the webserver to be able to serve the temporal UI.
Describe alternatives you've considered
We have an integrated product, so the other option would be to look at the APIs that the temporal UI calls and then replicate the UI logic and build our own frontend.
This would be a big investment and we would like to avoid it if possible.
Additional context
Requirement is very similar to https://github.com/temporalio/ui/issues/911
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing how the Temporal UI is served and how its asset and API URLs are formed; verify that it can be mounted under an arbitrary subpath when embedded in a Go server, with navigation and API calls remaining functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100