Build everything in production about digital-fuesim-manv HOT 8 CLOSED

Could you imaging doing this on the webserver level? So, e.g. nginx handles all requests. When it matches /api it gets redirected to port 3201 (HTTP server in the backend), where all other routes would be lead to 4200 (Angular). This would sound easier to me as we could deploy backend and frontend completely independent of each other, and plug them together using the webserver.

I don't see anything speaking against that.

from digital-fuesim-manv.

trying to get it into docker

from digital-fuesim-manv.

@ClFeSc what is your take about putting it into docker (at this stage)?

from digital-fuesim-manv.

I don't think it'd be a problem. We can just build everything and start it (from the dist, so not the watch modes) and expose the ports.

from digital-fuesim-manv.

During development, we are using angular's development server via ng serve. This server is not intended for production use.
Instead, the backend should:

• prefix all API routes with e.g. /api
• serve the build frontend files from the root path
• redirect all unknown paths to the root path and serve the index.html (opening on /abc would return the frontend, the frontend deals with the path (and possibly display a 404 page itself))

Look here for more information. This question could be helpful too.

from digital-fuesim-manv.

#144

first beginning, using this guide: https://www.indellient.com/blog/how-to-dockerize-an-angular-application-with-nginx/

not tested, need to get my docker environment right

from digital-fuesim-manv.

During development, we are using angular's development server via ng serve. This server is not intended for production use. Instead, the backend should:

* prefix all API routes with e.g. `/api`

* serve the build frontend files from the root path

* redirect all unknown paths to the root path and serve the `index.html` (opening on `/abc` would return the frontend, the frontend deals with the path (and possibly display a 404 page itself))

Look here for more information. This question could be helpful too.

Could you imaging doing this on the webserver level? So, e.g. nginx handles all requests. When it matches /api it gets redirected to port 3201 (HTTP server in the backend), where all other routes would be lead to 4200 (Angular). This would sound easier to me as we could deploy backend and frontend completely independent of each other, and plug them together using the webserver.

from digital-fuesim-manv.

• pass environment flags (whether production or not) to immer, socket.io, etc. (or make sure they use the Node environment)

from digital-fuesim-manv.