dev-to-production

问题 In Development-mode (APS-WebAPI) the build works perfekt without errors (ng b --watch). When change to production-mode (ng b --aot OR ng b --prod) the page loads without error but results in an empty page. The Index.cshtml would generated by searching the *.js-files in the folder from the Homecontroller. This problem occurs since we upgrade from Angular-6 to Angular-8. We would like to publish our changes and environment upgrade (Angular-8 & TypeScript 3.4.5). In Dev-mode (ng b --watch) we

问题 In Development-mode (APS-WebAPI) the build works perfekt without errors (ng b --watch). When change to production-mode (ng b --aot OR ng b --prod) the page loads without error but results in an empty page. The Index.cshtml would generated by searching the *.js-files in the folder from the Homecontroller. This problem occurs since we upgrade from Angular-6 to Angular-8. We would like to publish our changes and environment upgrade (Angular-8 & TypeScript 3.4.5). In Dev-mode (ng b --watch) we

问题 So this is a slightly insane idea that I've been kicking around. I'm thinking of building a classifier for (a specialized subset of) some web content, and then supplying it to users in the form of a chrome extension. (So: user goes to web page, clicks button on chrome extension, extension applies pre-trained model to generate prediction, presents result to user.) But I'm cheap, and I don't want to run a server to receive data from the chrome extension, generate a prediction, and send it back

问题 When I run webpack-dev-server, with a publicPath of /dist , I'm able to see live-edits for my app (changes to html, styling, js). However, when I compile the app into a production build, the stylesheet and javascript load from /dist/main.css and /dist/main.js instead of from main.css and main.js The problem seems to be with the publicPath setting. If I remove publicPath, the app compiles with main.css and main.js, but I'm not able to see live edits. However, if I keep publicPath: /dist I can

问题 I have 2 servers Both server's have the same php memory_limit of 128M of data. My Dev Server runs a script just fine, while on my prod server I am receiving a Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in ... My question is what are other reasons I would be running out of memory in the prod environment even though my php memory_limits are the same? 回答1: Preface PHP is module that runs top of Apache [HTTPD Server] this involves linking the php

问题 I'm testing out dev / prod config files using the method from the docs here https://webpack.js.org/guides/production/#simple-approach But when I switch my base config to a function I get the following error WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema. - configuration should be an object. Im using webpack 3.0.0 Original webpack.config.js const path = require('path'); const webpack =

问题 Problem Our deployed application has development dependencies in it. We have a lot of development dependencies. This increases the artifact size and the memory consumption in production, as all those dependencies are require 'd. Most instances are deployed in the cloud, so more memory = more money for larger instances. We would like to reduce the size/memory and make a more clear separation between the deployed artifact and the development environment. A particular focus is the need for

问题 I'm developing a little application using Symfony2. I can access all routes with no problems in my dev environment: http://symfony/app_dev.php/cp ("symfony" is in my hosts file to resolve to localhost) However, as soon as I try and access it in the production environment, I just get a 404 error page: http://symfony/app.php/cp Oops! An Error Occurred The server returned a "404 Not Found". Something is broken. Please e-mail us at [email] and let us know what you were doing when this error

问题 What I want to do now is to initialize a private repository on my production server in to app's www folder (ex: /var/www/app.com/web/) and then clone it as a staging repository to my testing site (ex: /var/www/test.com/web/app.com/) and finaly clone from staging to local to work with the code. Am I planning it the right way? I am following these tutorials to learn more about setting the "git server" and initialize private repositories: http://progit.org/book/ch4-4.html https://moocode.com

问题 I am using Extjs 5 ,sencha cmd 5 and extjs sencha charts. My app's index.html in the 'app' directory works fine,and sencha app build successfully. When I go to the production package to load the production index.html,the console gives me the error '.js not found' ,the log below: GET http://localhost:8080/build/production/recommendation/.js?_dc=1431411762018 404 (Not Found) Ext.Boot.Ext.Boot.d.fetch Ext.Boot.Ext.Boot.r.fetch Ext.Boot.Ext.Boot.r.loadSync Ext.Boot.Ext.Boot.r.load Ext.Boot.Ext