How to build for different environments using shake-build?

user_534481 0
Viewed 33

Is there a built-in way to pass command-line arguments to a "shakefile"? I'd like to pass --env production|development|staging and then use it within my rules to (slightly) alter the build-steps for each environment.

shake-build-system
1 Answers

There are two halves to this problem - first getting the flags into Shake, and secondly, using them to influence the behaviour.

You can get arguments into Shake using any Haskell command line parser, but Shake ships with support for one built it, which can often be easier:

data Flags = Production | Dev | Staging deriving Eq
flags = [Option "" ["production"] (NoArg $ Right Production) "Build production."
        ,Option "" ["dev"] (NoArg $ Right Dev) "Build dev."
        ,Option "" ["staging"] (NoArg $ Right Staging) "Build staging."
        ]

main = shakeArgsWith shakeOptionsn flags $ \flags targets -> do
    want targets
    ... do whatever you want with the flags ...
    return rules

For using the flags to influence, you might want to:

  1. Completely isolate build outputs from each flag, in which case changing the directory and setting shakeFiles differently in each case makes each one fully distinct.
  2. Use the flags to change the output paths, so you always have rules dev/main.js and prod/main.js, and then you consult the flags when doing want to pick up the right rules.
  3. Put the flags into an Oracle and have them as tracked settings, so when you flip from prod to dev some things rebuild.

If the builds are 80%+ distinct I'd go for 1. If you change flags very rarely 3 can work. Otherwise, I tend to opt for 2. But they all work, so picking the simplest to start with is also not unreasonable.

user_1606730
Related