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
There has been some internal discussions about extending nib to do more than simply wrap docker-compose commands. One of those ongoing discussions revolves around providing template generators for commonly used configurations. The idea is to provide sane and consistent defaults for new projects to be shared amongst a team of developers. Thinks like default configuration for CI tools or new project initialization (ie. the scaffold for a new Grape app).
There will need to be some thought put into this. For example, are these templates baked into nib or do you provide some configuration (url, directory) that points to the available templates for your team? I thought this would be a good place to further the discussion.
The text was updated successfully, but these errors were encountered:
There has been some internal discussions about extending
nib
to do more than simply wrapdocker-compose
commands. One of those ongoing discussions revolves around providing template generators for commonly used configurations. The idea is to provide sane and consistent defaults for new projects to be shared amongst a team of developers. Thinks like default configuration for CI tools or new project initialization (ie. the scaffold for a new Grape app).There will need to be some thought put into this. For example, are these templates baked into
nib
or do you provide some configuration (url, directory) that points to the available templates for your team? I thought this would be a good place to further the discussion.The text was updated successfully, but these errors were encountered: