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

[content-service] ability to exclude content from the backup of /workspace #15500

Open
kylos101 opened this issue Dec 23, 2022 · 3 comments
Open
Labels
component: content-service meta: never-stale This issue can never become stale

Comments

@kylos101
Copy link
Contributor

Is your feature request related to a problem? Please describe

Sometimes users add large files to workspaces at runtime, use them, and then delete them, to avoid backing up the files to Gitpod.

Keeping the backup size smaller helps keep workspace restarts fast, because then we do not have to download and untar unnecessary files from object storage.

Describe the behaviour you'd like

Provide a means to exclude file patterns from the backup of /workspace

Describe alternatives you've considered

  • Add the files to your .gitignore and delete them before stopping your workspace
  • Implement a pre-stop task, and delete files as part of that task

Additional context

leeway run dev:preview persists 20GB to the file system, but, we do not want to back it up, as an example

@kylos101
Copy link
Contributor Author

@atduarte how would you like this experience to work? I can see us allowing users to exclude files from the backup via .gitpod.yml. Another option would be to allow users to define pre-stop tasks.

@svenefftinge
Copy link
Member

svenefftinge commented Dec 31, 2022

I think this would be a good use case for a "stop" lifecycle hook (#3966).

@atduarte
Copy link
Contributor

atduarte commented Jan 2, 2023

@svenefftinge indeed. I believe we should start there, as it is the mechanism that covers the most use cases and "makes sense".

@kylos101 kylos101 added the meta: never-stale This issue can never become stale label Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: content-service meta: never-stale This issue can never become stale
Projects
No open projects
Status: No status
Development

No branches or pull requests

3 participants