2
Your question is very broad, so expect only to get a broad answer.
The general strategy for solving these kinds of problems is to make the requirements customizable. This can be done by introducing run time or compile time switches, configuration files, special code which is only used for a specific customer, "plugins", and so on.
From what you wrote, in ...
1
Performance is not the issue here. The real issue comes in when resolving the dependencies for the code using the "static" class (btw, a class is a Function object in JavaScript or just an object literal that can still be passed around like any other value).
If the "static" class is being pulled in to the page asynchronously using something like require.js ...
1
When it comes down to SSL configuration (or to be more correct HTTPS configuration) i would recommend you test your setup at https://www.ssllabs.com/ssltest/index.html and adjust to get an A grade or A+. Then you apply this config at your customers. HTTPS isn't such a dynamic topic that it changes every month. If your grade drops with the time do B it's ...
1
Some things will have to be set up on a machine by machine basis. The unfortunate truth is that TLS (the current version of SSL) is just tricky to get right.
If you have a number of servers to get set up, you can use Spring Cloud Configuration Server, which will help you centralize the configuration. It works well when you need to spin up another instance ...
1
Put the version number in its own file and don't ever merge that file.
Only top voted, non community-wiki answers of a minimum length are eligible
