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
Instead of a restart Rails app APPNAME resource, the default OpsWorks Node.js provides a restart node.js application APPNAME resource. (See here.)
Would you be opposed to supporting multiple application types in this cookbook? How would you like the type of an app to be defined in the configuration? Or, alternatively, is there another more generic resource that can be called instead of restart Rails app APPNAME?
The text was updated successfully, but these errors were encountered:
I don't know a great way to abstract the restart command from the custom_env_template definition while also skipping it when there are no changes. At worst, I suppose this cookbook could contain multiple recipes for different application types, each one notifying a service or executing a ruby block as necessary.
Do you know if it's possible to call notifies(:run, ...) in such a way that it can trigger the already-defined node restart block?
Instead of a restart Rails app APPNAME resource, the default OpsWorks Node.js provides a restart node.js application APPNAME resource. (See here.)
Would you be opposed to supporting multiple application types in this cookbook? How would you like the type of an app to be defined in the configuration? Or, alternatively, is there another more generic resource that can be called instead of restart Rails app APPNAME?
The text was updated successfully, but these errors were encountered: