-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Persistent state between workspaces #7025
Comments
There's a couple of things I'd love to see:
|
We are looking to adopt Gitpod with Pycharm for onboarding + development. The biggest friction seems to be that the IDE configuration doesn't persist on workspace restart. Features surviving workspace restart
Features not surviving workspace restart
Every time we restart a workspace, we need to configure the Python interpreter manually which in turn indexes the modules for this interpreter. It takes a total of 2 mins each time. I was able to persist Debug and Test configuration using the |
@abkunal Sorry for the late reply. I checked and these settings are stored as part of system config folder, so checking in of .idea folder is not enough. Could you try to follow https://www.jetbrains.com/help/idea/sharing-your-ide-settings.html to enable Settings Sync with JB account? |
Going to close this one, I think it duplicates So let's continue our discussion in those issues 🙏 |
@abkunal, thanks a lot for your feedback! 🙏
Yep, this one is an issue, created a dedicated one here for us to look into! 🙏
For this one, check out the dedicated issue, and current workaround we're using on Gitpod right now. |
Note: If we had discussions set up, this issue is more of a discussion than an issue/solution.
There are some situations where users need to have an element of persistence between their workspaces for the purpose of user configurations, and general continuity between the UX of a local env, and an ephemeral environment.
Some notable examples:
This feels like a similar challenge that serverless applications had to overcome, by allowing mounting of file systems as a temporary solutions "bridge" to allow users to move from a stateful paradigm to a serverless/ephemeral one [1].
The text was updated successfully, but these errors were encountered: