Handle projects which may have a server about generator-jam3 HOT 6 OPEN

or do we go with two separate repos? one for back end and one for frontend?

from generator-jam3.

I think separate repos makes more sense, probably won't be much code sharing
Also, scope creep!

from generator-jam3.

Not scope creep. 😁 It's a part of the long term plan. We've already been discussing backends and cmses that would work well with our workflow.

from generator-jam3.

Maybe we could have 2 generators: generator-jam3-frontend and generator-jam3-backend. In case you need both for the same project, you can create:

|-project-name/
|-- frontend
|-- backend

And then run the proper generator in each folder. With this maybe we loose the opportunity to have more advanced commands like yo jam3:update interacting with both projects at the same time. Maybe not. I'm not sure.

In the other hand, I think we should let this for phase 3 or 4 of the generator and just focus on front end at this point.

from generator-jam3.

I'm not sure separating the backend and frontend is a good route. By repo or by generator.

The holy grail of Node is to be able to use frontend code on the backend and backend code on the frontend.

One case where I've done thing many times is where I've setup a socket.io server and had an Object which stores all the "keys" for events in an Object. Like:

module.exports = {
  CHARACHTER_MOVED: 'charMoved'
}

On the frontend I'll listen for for events.CHARACHTER_MOVE and on the server I'll emit events.CHARACHTER_MOVE.

The game plan with the backend is to mirror the way we work with routes.

So if we have a section and route such as /about then the backend would also have an /about route you could call and get a JSON model for that section.

from generator-jam3.

Look into using salt for bringing in the latest php backends, look for a way to standardize backend code.

from generator-jam3.