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

feat: allow .env files in project directories to configure environment #9

Open
HipsterBrown opened this issue Jan 20, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@HipsterBrown
Copy link
Owner

Since one of the complexities of managing the xs-dev environment is making sure certain environment variables are sourced in the correct shell profile, maybe per-project configuration can use a conventional .env file to load into the process before certain commands like xs-dev run.

Along with existing configuration variables like UPLOAD_PORT, there could be a DEPLOY_TARGET or DEPLOY_DEVICE setting for the default --device (or platform target) for running projects.

@dashcraft
Copy link

I think a .env file is going to go a long way in improving build configurations with minimal effort. It could be mostly self documenting by naming convention.

I would probably prefer having default settings behind the scenes and then being able to override with a .env, than a .env per project.

@HipsterBrown HipsterBrown added the enhancement New feature or request label Mar 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants