SPA and Grails Project Organization Best Practices

[Mark Fortner]

I remember Bill saying at one of our meetings that a lot of their projects used SPA front-ends, and I was wondering how people typically organize these types of projects?  We're currently working on a project where the front-end resides in one git repo, and the Grails back-end resides in another.  When you check out the projects, they wind up as sibling folders in your workspace.

Since version 2.4, the asset pipeline plugin has been the canonical way of dealing with assets, but it doesn't seem capable of dealing with a sibling project whose contents need to be watched and repackaged/deployed periodically during the development process.  Currently the only way of deploying the project seems to be manually copying the code into the assets directory.  I know in Grails 3 the build system was shifted to gradle, and this type of thing is supposed to be easier, but I was curious how people are currently dealing with this situation, and if there are any best practices.

Regards,

Mark