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

Unable To Share a Workspace in a Self-Hosted Environment #6656

Closed
jimmybrancaccio opened this issue Nov 10, 2021 · 4 comments
Closed

Unable To Share a Workspace in a Self-Hosted Environment #6656

jimmybrancaccio opened this issue Nov 10, 2021 · 4 comments
Labels
meta: never-stale This issue can never become stale team: workspace Issue belongs to the Workspace team

Comments

@jimmybrancaccio
Copy link

Bug description

When attempting to share a workspace I see that an enterprise license is required. However I believe this is wrong as no enterprise license should be required for this functionality. I could be wrong though.

Screen Shot 2021-11-10 at 11 55 36AM

Screen Shot 2021-11-10 at 11 55 54AM

Steps to reproduce

  1. Spin up a self-hosted Gitpod instance based on v0.10.0.
  2. Spin up a new workspace.
  3. Click on the 3 bars in the upper left corner which should display a menu.
  4. Observe underneath the horizontal divider there are five "Gitpod" options, with the fourth option being "Gitpod: Share Running Workspace". Click that option.
  5. Observe a popup letting you know you will be sharing the workspace and repository. Click on the Share button.
  6. Observe in the lower right corner a popup notification stating that an enterprise license is required.

Workspace affected

No response

Expected behavior

I expect that workspace sharing work even if I don't have an enterprise license.

Example repository

No response

Anything else?

This issue stems from a post on the forums:

https://community.gitpod.io/t/timeout-and-sharing-with-gitpod-self-hosted/5570

@iQQBot
Copy link
Contributor

iQQBot commented Nov 11, 2021

Currently the code is not adapted to less than 10 people free

@jldec jldec added the team: workspace Issue belongs to the Workspace team label Nov 12, 2021
@stale
Copy link

stale bot commented Feb 12, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Feb 12, 2022
@jimmybrancaccio
Copy link
Author

@Stale No.

@mrsimonemms
Copy link
Contributor

This is fixed by #8328 which will be part of the March 2022 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: never-stale This issue can never become stale team: workspace Issue belongs to the Workspace team
Projects
No open projects
Archived in project
Development

No branches or pull requests

5 participants