I am trying to render a landscape locally for test purposes. Unfortunately when I attempt to run a render, during yarn fetch, specifically at the addExternalInfo.js step, all the crunchbase data from the processed landscape is lost, despite the output saying:
CRUNCHBASE_KEY_4 is not set. Using processed_landscape.yml as a source for crunchbase info
I'm pretty sure this didn't happen when I first tried playing with Landscapeapp, though perhaps it always had. Either way, this isn't very helpful when I need to run builds locally to test the effect of changes to landscapeapp and want to ensure I'm not breaking official landscapes in doing so.
Is there a convenient way for me to ensure that the already cached data is not lost so that I can render these landscapes locally?
I am trying to render a landscape locally for test purposes. Unfortunately when I attempt to run a render, during
yarn fetch, specifically at theaddExternalInfo.jsstep, all the crunchbase data from the processed landscape is lost, despite the output saying:CRUNCHBASE_KEY_4 is not set. Using processed_landscape.yml as a source for crunchbase infoI'm pretty sure this didn't happen when I first tried playing with Landscapeapp, though perhaps it always had. Either way, this isn't very helpful when I need to run builds locally to test the effect of changes to landscapeapp and want to ensure I'm not breaking official landscapes in doing so.
Is there a convenient way for me to ensure that the already cached data is not lost so that I can render these landscapes locally?