Skip to content

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

Closed
@david-bakin

Description

@david-bakin

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions