What should I put in a separate repository?

Project structure:
├── bower_components
├── node_modules
├── build <- the Folder with the compiled frontend
├── gulp <- Folder with her gulp and settings (only for frontend)
├── migrate <- folder with the import files for MongoDB when you first start the server
├── server <- Folder with files to the server
├── src <- Folder for the source code of the frontend
├
├── LICENSE
├── LINKS.md
├── README.md
├── TODO.md
├── bower.json
├── gulpfile.js
├── package.json


Need something nice to split the repository into 2 parts.

git submodule never used, so I'm asking how to do it, to be comfortable.
Server any pages not renders only JSON RESTapi gives. And the statics of the folders build and bower_components.
Frontend gulp-om going from src to build. What should I put in a separate repository?

As I understand it:
Make the frontend in a separate turnip and turnips polychem server something like this:
git submodule add git://github.com/username/frontend.git frontend

And in the script server write this:
app.use(express.static(path.join(__dirname, 'frontend/build')));
app.use('/bower_components', express.static(path.join(__dirname, 'frontend/bower_components')));


But then changing the files for the frontend I don't just gulp build should be carried out, and even commit, and turnips servers something like git submodule update.
July 9th 19 at 13:25
1 answer
July 9th 19 at 13:27
Server individually, front separately. But if the front is generated by the server, why invent a problem?

I'd recorded only releases the front and a server synchronously, which would be the case then you could revert to stable production, according to various repositories of course, not every time the front generate.

But then changing the files for the frontend I don't just gulp build should be carried out, and even commit, and turnips servers something like git submodule update.

And so, there is a gulp-git package.
For gulp-git thanks, I'll try. Yes I already figured out. I don't really want to do right now, as I do. Server for static front you can use anything. At the same Node.js 30 lines written. And since it has a API server to send requests. And associate them was stupid. Further, mobile clients are planned, so that will go to untie the front of the server. - Kameron_Hilpert34 commented on July 9th 19 at 13:30
In the case of applications node.js the fronts do the vast majority of cases is generated by the server because of the use of templates, minimization and layout, js, etc., etc - abigail36 commented on July 9th 19 at 13:33
: front on my Angularи is generated by gulp-ohms at Assembly )) From the server I just need RESTapi - Kameron_Hilpert34 commented on July 9th 19 at 13:36

Find more questions by tags GitNode.js