Fullstack repo

As evidenced by this issue, wiring up frontend and backend can be non-trivial. It would be useful to have a single repo that I could clone, and say npm start and it would give me both a running backend and frontend.

This repo could depend on appropriate BE and FE repos via package.json. E.g. something like:

{
  "name": "realworld-fullstack-node-angular",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "start": "node ./start_fullstack.js"   <---- all your base are belong to us
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "conduit-angularjs": "https://github.com/gothinkster/angularjs-realworld-example-app",
    "conduit-node": "https://github.com/gothinkster/node-express-realworld-example-app"
  }
}

[anishkny]

I would think docker-compose would be great for this? Assuming we standardize each stack’s specification using Docker.

[Cameron-C-Chapman]

I wonder if some standardized sections in the readme like “startup prerequisites” and “startup” along with some standardization around things like port numbers to use could help? That way if a project is getting merged those startup instructions can be validated and the port numbers are always common so swapping out backends is trivial. Say for example front ends are always 9000, backends are always 9001, and the db’s are always the db specific default?