Add a way to specify a non-default `static.config.js` to use

[crubier]

Hi, I would like to be able to configure react-static a bit more, because i would like to compile two sites from the same codebase.

For this I need to be able to put two static.config.js files with different names in the root of my project.

Putting two static.config.js files in two different directories is not an option, as it breaks up the node_module resolution beyond hope of repair (Believe me, I tried... and all I learnt was that react-static does waaay too much magic with node_modules to my taste)

[EmilTholin]

Hi @crubier!

Maybe you could use an environment variable of your own for the time being?

package.json

{
  "scripts": {
    "build:first": "cross-env MY_ENV_VAR=first react-static build",
    "build:second": "cross-env MY_ENV_VAR=second react-static build"
  }
}

static.config.js

if (process.env.MY_ENV_VAR === 'first') {
  // ...
} else {
  // ...
}

export default {
  // ...
};

[crubier]

Ok, this seems like a good idea, but I found a bug while doing this: #224

[stale]

This issue has been automatically marked as stale because it has not had recent activity in 7 days. It will be closed if no further activity occurs. Thank you for your contributions.

[tannerlinsley]

Still need to get to this.

…

On Sat, Jan 6, 2018 at 7:42 AM stale[bot] ***@***.***> wrote: This issue has been automatically marked as stale because it has not had recent activity in 7 days. It will be closed if no further activity occurs. Thank you for your contributions. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#223 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFUmCda4bUyEubkHotxGWpxZ6i2x9Srgks5tH4ZpgaJpZM4Q5cw-> .

[stale]

This issue has been automatically marked as stale because it has not had recent activity in 7 days. It will be closed if no further activity occurs. Thank you for your contributions.