User Blocked Page in Self-Hosted Instance Advises User To Contact Gitpod.io Support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
When a user is blocked in a self-hosted instance they're shown a page that lets them know they're blocked with a button to 'Contact Support' and a link to review the Terms of Service on the Gitpod website.
We likely need to allow instance administrators to set an email address of their own or URL which can be used in these sorts of situations where the user is being told to contact support.
Steps to reproduce
- Spin up a self-hosted instance - using
2022.05.2. - Create a few users and block one of them.
- Login as the blocked user and attempt to spin up a workspace.
- Observe the page telling you you're blocked and that you can view the Terms of Service and a Contact Support button. Note these link to Gitpod.io.
Workspace affected
No response
Expected behavior
I would expect in a self-hosted environment I can view the terms of service for that environment, and when clicking on Contact Support that I am contacting the support of that instance, not Gitpod.io.
Example repository
No response
Anything else?
I believe the related code is here - https://github.com/gitpod-io/gitpod/blob/c2a621ef64571a26805fe7f1ffb2d4cea3accf42/components/dashboard/src/App.tsx#L299
Contributor guide
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
Start in components/dashboard/src/App.tsx around line 299, then trace how the blocked-user page obtains its Terms of Service and Contact Support links. Check how self-hosted instance settings are represented before determining where instance-specific values belong. Done means blocked users in self-hosted environments see that instance's terms and support destination rather than Gitpod.io links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100