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
hammer-io should change the way that projects are organized. Currently, hammer-io only allows for projects to be created and there is no way to create a family of projects.
What
The following format should be used:
Product:
A collection of services and libraries. A product would have a feed of ALL of the activities from the services and libraries. This include commits, pull requests, issues, builds, etc.
Services
A project which runs a service. When creating a service it should allow for options for selecting a web framework, containerization tool, and deployment tool.
Libraries
A library is a project which does not run a service. This might be a custom logging tool, or glue code to connect microservices. In other words, its any project that does not run a server.
Why
Managing monorepos are hard, but managing many projects is difficult to
A consolidated view of all of the happenings in the entire product
More easily manage the dev ops over the whole product
How
Allow for the option to create a product
Allow for the option to create a project underneath a product
Allow for choosing the project to be a service or library than conditionally display the proper tooling options
The text was updated successfully, but these errors were encountered:
hammer-io should change the way that projects are organized. Currently, hammer-io only allows for projects to be created and there is no way to create a family of projects.
What
The following format should be used:
Product:
A collection of services and libraries. A product would have a feed of ALL of the activities from the services and libraries. This include commits, pull requests, issues, builds, etc.
Services
A project which runs a service. When creating a service it should allow for options for selecting a web framework, containerization tool, and deployment tool.
Libraries
A library is a project which does not run a service. This might be a custom logging tool, or glue code to connect microservices. In other words, its any project that does not run a server.
Why
How
The text was updated successfully, but these errors were encountered: