I've started to notice a pattern where the user interface is served from within a directory in the resources. This works really well when dockerizing the application with jib. It would make sense for there to be a UI router that's available in the framework.
Should this be a different module? I picked swim.services.web mainly because it fit with the dependencies that I cared about. Should this go in it's own module?
I've started to notice a pattern where the user interface is served from within a directory in the resources. This works really well when dockerizing the application with jib. It would make sense for there to be a UI router that's available in the framework.
Should this be a different module? I picked swim.services.web mainly because it fit with the dependencies that I cared about. Should this go in it's own module?