production

问题 I'm building a single page app using webpack. Have seen several times that it is recommended to extract css from production build but didn't find the reason. Could anyone explain why it is treated as a best practice and what the advantages of that for production? Is it needed for caching styles and js separately on client only or there are other reasons, cons, pros? An example of such recommendation you can find by link below https://github.com/webpack-contrib/sass-loader In production

问题 Is it worth designing a system to expect test accounts and products to be present and active in production, or should there be no contamination of production databases with test entities, even if your shipping crew knows not to ship any box addressed to "Test Customer"? I've implemented messaging protocols that have a test="True" attribute in the spec, and wondered if a modern schema should include metadata for tagging orders, accounts, transactions, etc. as test entities that get processed

问题 There are many ways of deploying Mule ESB into a production environment. According to the documentation, it appears that running Mule as a standalone service is the recommended way of doing so. Are there any reasons for NOT running Mule standalone in production? I'm sure its stable, but how does it compare to Tomcat as far as performance, reliability, and resource utilization go? Should I still consider running it within Tomcat for any reason? 回答1: Using Tomcat, or any other web container,

问题 I am new in angular 2, I want to know how to build my angular 2 app without using CLI for production. Thanks in Advance. 回答1: If you have used CLI for your existing application You can migrate from Angular CLI to Webpack and tweak it accordingly for (local, development, production). Since Angular CLI v1.0 there’s the “eject” feature, that allows you to extract the webpack config file and manipulate it as you wish. Run ng eject so Angular CLI generates the webpack.config.js file. Run npm

问题 My ruby on rails action mailer runs all good in development environment, but in production environment, it keeps throw: ActionView::Template::Error: Missing host to link to! Please provide the :host parameter, set default_url_options[:host], or set :only_path to true My development config is config.action_mailer.delivery_method = :smtp config.action_mailer.smtp_settings = { :port => xxx, :address => 'smtp.example.org', :user_name => 'xxx@example.com', :password => 'xxxxxxxx', :domain =>

问题 Say I have a website and a database of that website hosted locally on my computer (for development) and another database hosted (for production)...ie first I do the changes on the dev db and then I do the changes to the prod DB. What is the best way to transfer the changes that I did on the local database to the hosted database? If it matters, I am using MS Sql Server (2008) 回答1: The correct way to do this with Visual Studio and SQL Server is to add a Database Project to the web app solution.

问题 I have a small project written in Angular 7 and im trying to build the production version out of it. When i run ng build --prod --aot --service-worker The build will run without errors as seen on screenshot. On the other hand, when im trying to load the app in the browser, it will throw errors in console and will not load at all. Any ideas what is causing this? The files are in the same directory as the index.html and they do exist. 回答1: So, I figured out that if I want to serve this files

问题 Time to time when i access the production site the site is down. I dont know how much time it has been down for. I then ssh to the production server and check the logs and the logs has no record of when the puma was down. I do grep 'puma shutdown:' puma.error.log to see all instances of when puma was shutdown === puma shutdown: 2018-03-18 15:44:20 +0545 === === puma shutdown: 2018-04-27 15:22:14 +0545 === === puma shutdown: 2018-04-28 18:27:26 +0545 === === puma shutdown: 2018-05-08 17:45:37

问题 Why am I getting an "Unknown provider: e" error when hosting a production version of an Angular 7/AngularJS hybrid app in IIS? I have an Angular 7/AngularJS hybrid app that I'm running. Everything runs fine in development mode using "npm start". However, after building a production version, the page gives me a [$injector:unpr] Unknown provider: e error. I've tried only running the Angular 7 code and that works fine. I've tried debugging and my angularjs code in an app.js file is being

问题 Why am I getting an "Unknown provider: e" error when hosting a production version of an Angular 7/AngularJS hybrid app in IIS? I have an Angular 7/AngularJS hybrid app that I'm running. Everything runs fine in development mode using "npm start". However, after building a production version, the page gives me a [$injector:unpr] Unknown provider: e error. I've tried only running the Angular 7 code and that works fine. I've tried debugging and my angularjs code in an app.js file is being