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

[Self-Hosted] Unable to set workspace timeout when having > 10 users #10270

Closed
shaoye opened this issue May 26, 2022 · 2 comments
Closed

[Self-Hosted] Unable to set workspace timeout when having > 10 users #10270

shaoye opened this issue May 26, 2022 · 2 comments
Labels
meta: stale This issue/PR is stale and will be closed soon team: delivery Issue belongs to the self-hosted team

Comments

@shaoye
Copy link
Contributor

shaoye commented May 26, 2022

According to https://www.gitpod.io/self-hosted, we're currently advertising all self-hosted instances without any timeout

So, options are:

  1. change the webpage to say "30m or 60m timeout"
  2. remove the timeout entirely (or, if that doesn't work, set to 1 year)

As I'm currently doing #8328, it makes sense to do this now. Personally, I favour option 2

image

Hi, it would be great if gitpod adopts option 2 (I think it's a yes according to the latest pricing page).

But currently we are still unable to modify the timeout option (EE licence required https://github.com/gitpod-io/gitpod/blob/main/components/server/ee/src/workspace/gitpod-server-impl.ts#L295)

Do we have an open issue for tracking this? thanks!

Originally posted by @shaoye in #8528 (comment)

@shaoye shaoye changed the title [Self-Hosted] Unable to set workspace timeout [Self-Hosted] Unable to set workspace timeout when having > 10 users May 26, 2022
@shaoye
Copy link
Contributor Author

shaoye commented May 26, 2022

I think it is being tracked here #9038

@stale
Copy link

stale bot commented Sep 9, 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 Sep 9, 2022
@stale stale bot closed this as completed Sep 25, 2022
Repository owner moved this from 🧊Backlog to ✨Done in 🚚 Security, Infrastructure, and Delivery Team (SID) Sep 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon team: delivery Issue belongs to the self-hosted team
Projects
No open projects
Development

No branches or pull requests

2 participants