Skip to content

Add doc page(s) for "hints and tips" for getting stuff to work with gitpod #12185

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

Closed
david-bakin opened this issue Aug 18, 2022 · 3 comments
Closed
Labels
feature: documentation meta: stale This issue/PR is stale and will be closed soon

Comments

@david-bakin
Copy link

david-bakin commented Aug 18, 2022

Add specific easy-to-find pages for hints and tips for getting stuff to work with gitpod. Specific stuff.

E.g., people frequently discover that things that they do in a start task aren't persisted - why? because only /workspace is persisted (specifically /home/gitpod is not persisted, nor is anything in /usr/ and so on).

This is documented but people have trouble with specific tools. E.g., npm which puts stuff by default into /usr/local (apparently, or at any rate not in /workspace).

All these tools have supported workarounds - environment variables, or command line arguments, or config files, or something - that control where they install stuff, or look for stuff.

So the suggestion is: Have a page that explains this. E.g., it would say if you're using brew then by default it installs stuff in /usr/local which is fine in your custom Dockerfile but not in your .gitpod.yml - you've got to actually install brew into /workspace if you want brew-built packages to persist. And pyenv wants to put stuff - I forget where, I think your home directory - but you can set the env var PYENV_ROOT to where you want it to put things. And so on and so forth.

And then this page can have other hints and tips too about configuring specific stuff to work specifically in gitpod workspaces...


- these issues frequently come up on the discord channels

@axonasif
Copy link
Member

Hey @david-bakin, thanks for writing that up. I'm going to include your issue on #10701

@stale
Copy link

stale bot commented Jan 2, 2023

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 Jan 2, 2023
@pawlean
Copy link
Contributor

pawlean commented Feb 15, 2023

Lou is working on this in this draft PR: https://github.com/gitpod-io/website/pull/2950

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: documentation meta: stale This issue/PR is stale and will be closed soon
Projects
Status: Done
Development

No branches or pull requests

3 participants