builder-web: Added --cachedir CLI param for staging new vizs #102

There is no content yet.

Intention is to pass a custom cache-dir when staging new vizs to test them - but still run up against the production data-dir

I don't quite understand the issue you're trying to solve... Is this related to what we talked about versioning and migration?

The scripts in packaging also need to be changed to optionally use this parameter

I don't quite understand the issue you're trying to solve... Is this related to what we talked about versioning and migration?

The issue is that we on shell.robur.io run a 'production' builder-web and a 'staging' builder-web - both running up against the same builds directory. This makes it possible to test a new version of builder-web with all the data.

The problem arises if one wants to test new visualizations @ staging and still use the same builds directory. Currently, if one changes the cache of vizs @ staging, one changes it for production too.

Great, looks good to me apart from minor nits. :)

I added a commit addressing the minor nits. This is fine to merge!

   let cachedir = match cachedir with
     | Some c -> Fpath.v c
     | None -> Fpath.(datadir / "_cache")
   in

       $ influx
       $ port $ host
       $ datadir $ cachedir $ configdir
     ) in

   | `Linux -> "/var/lib/builder-web"
 let default_cachedir =
   default_datadir ^ "/_cache"