You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 2, 2019. It is now read-only.
If I need to tweak the setup function from the nodejs strategy, I shouldn't need to create a custom strategy. Overloading specific strategy functions in the config file would make the entire experience a lot neater.
The text was updated successfully, but these errors were encountered:
Take the following .deliver/config taken from a production node.js app (uses deliver v0.6.0-pre):
#!/usr/bin/env bashSERVER="nodejs-1"APP="analytics_api"PORT="5010"STRATEGY="nodejs"AUTHORIZED_REMOTE_HOSTS+=("bitbucket.org")npm_install(){status"Setting up nvm & npm modules"__remote" cd $DELIVER_TO bin/setup "}
I've replaced the default npm_install() function by adding nvm logic and a few extra steps, all encapsulated in that app's bin/setup. It's that simple!
If I need to tweak the setup function from the nodejs strategy, I shouldn't need to create a custom strategy. Overloading specific strategy functions in the config file would make the entire experience a lot neater.
The text was updated successfully, but these errors were encountered: