https://github.com/dword-design/gitpod-env-per-project
GitPod helper command for project-specific environment variables.
https://github.com/dword-design/gitpod-env-per-project
conflict gitpod helper multiple naming per project repository scope specific variable variables
Last synced: 2 months ago
JSON representation
GitPod helper command for project-specific environment variables.
- Host: GitHub
- URL: https://github.com/dword-design/gitpod-env-per-project
- Owner: dword-design
- License: other
- Created: 2021-04-08T16:26:51.000Z (about 4 years ago)
- Default Branch: master
- Last Pushed: 2025-02-21T05:03:21.000Z (3 months ago)
- Last Synced: 2025-03-17T11:35:32.217Z (2 months ago)
- Topics: conflict, gitpod, helper, multiple, naming, per, project, repository, scope, specific, variable, variables
- Language: JavaScript
- Homepage:
- Size: 1.45 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Funding: .github/FUNDING.yml
- License: LICENSE.md
Awesome Lists containing this project
README
# gitpod-env-per-project
GitPod helper command for project-specific environment variables.
GitPod by default does not support variables with the same name but different scopes. E.g. setting a variable `API_KEY` for scope `user/project1` and setting a variable `API_KEY` for scope `user/project2` will lead to the first variable being deleted. But you often want to have project-specific variables with the same name.
This tool iterates all environment variables and replaces the ones with a project-specific prefix with their non-prefixed forms.
`PROJECT1_API_KEY` -> `API_KEY`
## Install
```bash
# npm
$ npm install -g gitpod-env-per-project
# Yarn
$ yarn global add gitpod-env-per-project
```
## Usage
The tool assumes that all project-specific variables are prefixed by `PROJECT_`, where `PROJECT` is the [constant-case](https://github.com/blakeembrey/change-case/tree/master/packages/constant-case) form of the package name.
Let's assume you have the following name in your `package.json`:
```json
{
"name: "@scope/project"
}
```
Calling `gitpod-env-per-project` returns the following string, similar to [gp env](https://www.gitpod.io/docs/environment-variables#using-the-command-line-code-classlanguage-textgp-envcode):
```
PROJECT_FOO_BAR=
FOO_BAR="value"
```
When calling `eval $(gitpod-env-per-project)`, it actually sets the variables in the environment.
## Contribute
Are you missing something or want to contribute? Feel free to file an [issue](https://github.com/dword-design/gitpod-env-per-project/issues) or a [pull request](https://github.com/dword-design/gitpod-env-per-project/pulls)! ⚙️
## Support
Hey, I am Sebastian Landwehr, a freelance web developer, and I love developing web apps and open source packages. If you want to support me so that I can keep packages up to date and build more helpful tools, you can donate here:
If you want to send me a one time donation. The coffee is pretty good 😊.
Also for one time donations if you like PayPal.
Here you can support me regularly, which is great so I can steadily work on projects.
Thanks a lot for your support! ❤️
## License
[MIT License](https://opensource.org/licenses/MIT) © [Sebastian Landwehr](https://sebastianlandwehr.com)