livecycle / livecycle/preevy

[Feat]: Passing ENV variables to preevy up

Open
#541 3 comments 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
2.2k
Forks
91
PR merge metrics
No merged PRs in 30d

Description

### What feature?

Maybe I missed it in the doc, and in the example the docker-compose has hardcoded `env`. In most setups we need to specify differente ENV based on the environment. Is there a way to do this?

### Describe the solution you'd like

Ability to pass environment variables or file to the `preevy up` command and/or GitHub action

### Describe alternatives you've considered

Configuring env on third party service and retrieve them on startup. Not sutable for every project

### Additional context

_No response_

### Add screenshots

_No response_

### Record

- [X] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.