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

Config Flag #60

Closed
BryanSchuetz opened this issue Dec 8, 2022 · 3 comments
Closed

Config Flag #60

BryanSchuetz opened this issue Dec 8, 2022 · 3 comments
Assignees
Labels
wontfix This will not be worked on

Comments

@BryanSchuetz
Copy link

Is it possible to pass a --config flag to the build command? Say, if we want to use an alternative config file for production builds?

@yoannchaudet
Copy link
Collaborator

yoannchaudet commented Jan 9, 2023

👋 Not without some changes. One thing you could easily do though is:

  • Use your own worklfow to deploy your site
  • Add an extra step to select the right configuration file based on the environment (e.g. by renaming a production_config.yml into _config.yml)

@BryanSchuetz
Copy link
Author

So check for an environment variable and then rename the associated config file to use the default name... that's an interesting idea. Thanks.

@JamesMGreene JamesMGreene added the wontfix This will not be worked on label Jun 21, 2023
@JamesMGreene JamesMGreene self-assigned this Jun 21, 2023
@JamesMGreene
Copy link
Contributor

Closing this out as a wontfix for now since there is a viable workaround. 👍🏻

Folks should feel free to open a new issue if this becomes a blocker, though. 👂🏻

@JamesMGreene JamesMGreene closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants