Unified servers under one source control #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Arseniy,
Great tutorial you put together. I really appreciated going through it. I'm still learning Angular, Express and Bootstrap and reviewing your post helped.
Since I'm new to this world, I'm not sure about best practices, etc. One thing that confuses me is maintaining two separate code bases for client and server in Development when in the end they are served out of the same application in Production. To that end, I fell upon a method to maintain and run two servers out of one code base. I thought I'd fork and update your code to allow that. I put together a repository that explains how to do this, mostly so that I can remember when I need it again.
In addition, a feature in webpack allows proxying of requests from the Angular development server to the separately running express server, which obviates the need for CORS. I added that capability, as well. You can see the change in
proxy.conf.json
andangular.json
.Please feel free to merge these changes, if you find them of value.
Cheers,
Andy