dotsh filesync can help with persisting auth for almost all* programs, so that you don't have to re-auth each time a Gitpod workspace is launched. All of the examples/instructions below are to be followed inside a Gitpod workspace to setup persistence.
If you're looking for including/installing persistent tools inside a workspace, see easy package installation.
Please follow Quickstart for gitpod if you're not using dotsh and want to use the below examples.
# To login
docker login
# To persist
dotsh filesync save -dh ~/.docker/config.jsonYou can also check this loom if you want a visual guide.
# To login
# Make sure to select 'N[o]' when it asks about launching a browser
doppler login
# To persist
dotsh filesync save -dh ~/.doppler/.doppler.yamlIf you're looking for examples that doesn't use dotfiles to setup doppler but rather configure in repo level, here are a few:
- https://github.com/jimmybrancaccio/gitpod-doppler-test
- https://github.com/gitpod-samples/demo-secrets-management
# To login
gcloud auth login --no-launch-browser
# To persist
cd ~/.config/gcloud
dotsh filesync save -dh access_tokens.db active_config configurations credentials.dbNo manual login/persistence is necessary when using dotsh as your dotfiles installer[1].
Note: You can set DOTFILES_GITHUB_TOKEN or DOTFILES_GITLAB_TOKEN at https://gitpod.io/variables with */* scope to use a custom token other than the one provided by Gitpod.
# Simply save the gnupg dir after creating keys
# And after this you could sign your commits easily without having to set gnupg each time.
dotsh filesync save -dh ~/.gnupg# To login
npm login
# To persist
dotsh filesync save -dh ~/.npmrcHave an example that you'd like to add? Feel free to raise a pull request 🙌