Geek asks and answers

MEAN Project - Organization

I am wondering what are your best methods for a single web page application project using the MEAN stack (MongoDB, Express, Angular and Node.js).

Now we have the following organization:

  • One Git Repository for Angular Client Code
  • One Git repo for Node.js and server-side code.

I saw browsing some blogs and checking the node.js template that the general structure should have only one repository to process Angular code and server code.

I would like to know from the community if this approach is really better than having two difference repos in terms of version control, easily deployed, etc.

From my personal point of view, I do not see such a big difference ...

+3
source share
1 answer

I don’t see much difference either. In fact, this should lead the team. Your code organization can be useful if you have separate front-end and back-end commands. I saw the environment when the user interface only loaded part of the user interface and connected to the REST server deployed somewhere on the DEV server.

Number 2 is the release procedure. If your external interface and back panel are tightly connected, they will be released together 99%. Then you do not need to process 2 repositories. However, if your back-end will serve as the endpoint of the REST service for other clients, not only your user interface, and you plan to release interface changes without touching the internal ones (without downtime for external clients), you may want to use two separate repositories.

CI. , . CI , , .

+1

More articles:


All Articles