You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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”.
The text was updated successfully, but these errors were encountered:
alexec
changed the title
Env file suppoet
Env file support
Oct 9, 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!
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”.
The text was updated successfully, but these errors were encountered: