I would use a separate repo for the backend and the frontend and use buildout to compose the environment. The buildout project would then install your repos and setup locally your frontend tools using ree's buildout conf. Then you'll still use your package & bower json files as you would do. You'll then be able to use grunt dev server for your front end development or, like Tres proposed, add an includeme function and make your frontend package easily addable to your backend app and expose it as static files.
On Tuesday, April 22, 2014 8:53:06 AM UTC-4, Achim Domma wrote: > > Hi, > > I want to develop a REST service using Pyramid + Cornice. The UI should be > implemented in AngularJS. I'm quite happy with my "normal" Pyramid/Python > workflow using virtualenvs, pserve for local development, ... The tool of > choice in the Javascript world seems to be http://yeoman.io/ The service > and the ui are of course seperated in theory, but they build one project > and I want to manage them together. Service and UI will be served from the > same domain, so that I don't have to care about cross domain access stuff > like CORS. I would like to have the same for my development system, so I > would have to "build" the Javasript files into my Pyramid project. > > I just wonder if somebody else has some recommendations how to organize > that kind of project. I found no template or scaffold which seems to fit > the use case, but I assume I'm not the first person with this problem. Any > starting point would be very apprecidated! > > cheers, > Achim > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
