Skip to content
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

Env file support #39

Open
alexec opened this issue Oct 9, 2023 · 1 comment
Open

Env file support #39

alexec opened this issue Oct 9, 2023 · 1 comment

Comments

@alexec
Copy link
Collaborator

alexec commented Oct 9, 2023

If you want to change many environment variables at once you need to give them all. It is verbose. It might be nice to have .env files imported, e.g. “kit -e test” would import “test.env”.

@alexec alexec changed the title Env file suppoet Env file support Oct 9, 2023
@agilgur5
Copy link

agilgur5 commented Oct 10, 2023

For reference, Task has this built into its spec. You can list one or multiple env files under the dotenv keyword at both the top-level and the task level.
I think that option is more flexible and simpler than CLI args if you plan to add that.

In general, Task's spec is pretty comprehensive (outside of the key process management things that kit can do). Would be cool if their specs were even more closer to each other!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants