Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Should I create multiple docker containers to host my frontend and backend source code?
With traditional approach (Nginx and Reverse proxy in Ubuntu) I don't separate them. What's the advantage of separating both?
Yes, it's a good practice to achieve resilience, here where I work, we run 3 instances of the same container, and in the front of then, we have a load balancer, with that, if one instance is down, we have other 2 to receive the traffic.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I want to know the best folder structure for typescript-express backend project.
Presently i am fallowing the bellow structure.
src-
-controllers
-models
-middleware
-utils
I am generally following this guide: https://gist.github.com/tracker1/59f2c13044315f88bee9
This can be applied to most javascript projects (nodejs or frontend-only) and is (kind of) used by a lot of CLIs like the vue and react cli.
Your controllers, models etc. should therefore be inside the SRC folder.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
What is the best method to bring a gigantic JS object to client side?
This is not a good idea. You are going to bloat your website / application size and it will run very slowly.
You are better off putting that object either into a database or at least server side in some form and making API calls to just the data you need, when you need it.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I struggle to find any suggestions how to organize RactiveJs code.
Currently I just put RactiveJs code to the bottom of the page. It was okay till my scripts were small. But the bigger they are the more problem it causes. I'm considering moving the RactiveJs code to separate js files, may be using some pattern (Module?).
Are there any guidelines in this regards?
There is a spec for component-per-file: https://github.com/ractivejs/component-spec/ and there are loaders that allow you to incorporate them into the page.
However, Ractive doesn't force you to use this pattern. You are free to experiment whatever convention works for you.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am starting a new Android app, and I would like to know what should be the best server-side stack that I could use.
I heard some about MeanIO, MeanJS, Cleverstack, Generator Angular Fullstack.
Which of these suggestions should be the best? Is there another one that is not on the list that would be even more interesting?
If I am correct in saying it depends in what you're doing and trying to focus on. If you wish to also build a web-based front-end it's probably necessary to include AngularJS. If you aren't planning on doing that you could probably cut out the need for Angular.
I imagine the MEAN stack (https://github.com/meanjs/mean) would be enough for your Node.JS server. I doubt you will need to use Angular for an android app so you will be more focused upon the Express+Node+Mongodb portions.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
What are the advantages of using requireJS if all the script files are merged into one in production?
Im working on a multiple page project.
You only merge the files for staging and production. In development you keep them separate.
This lets you manage your JavaScript by dividing it into discrete units. This makes it easier to test, easier to reuse and easier to find the piece of code you need to change.