Add option to install Stork during CI builds. #9
Comments
How about this plugin can configure for an optional env variable say - Once that is done, when actually invoking stork for index creation - similarly we can use either How does that sound ? Would that be a trivial fix? For ease and reducing complexity with the plugin, We can simply ask the client to set the env variable to correct binary executable location (along with chmod +x). Since most will anyways only use this for CIs, this should be quite easy for them to set as well. @reese |
I think the ENV variable sounds reasonable to me, especially for a quick fix for your use case. In the long term, I think it could also be useful to provide a default installation script during CI and then expose a config flag to optionally run it. There's an |
@ashutoshsaboo I'll work on a more robust solution in the future, but I just published version |
Many users will deploy this using Github Actions, Netlify, or similar build providers. Installing Stork during CI builds by default (and allowing users to opt-out if needed) would save many users some headaches.
The text was updated successfully, but these errors were encountered: