production-environment

Imagine you have your web application and some workflow executors: http-server (serving pre-build asset files) - production builder (compiling/bundling js/css/html from sources) - deployment/development debugger/builder (building from sources on the fly, add js source maps) - development selenium (running tests) - integration testing How can we construct layered images to get those workflow executors working the most effectively? By effectively I mean "fastest to run and least to write". The answer might be straightforward: just create 4 Dockerfile s one depending on another. You can add a

I have a PHP script that fetches an image from a remote server so that I can manipulate it using HTML5 canvas API. <?php if ((isset($_GET['url']))) { $url = $_GET['url']; $file_format = pathinfo($url, PATHINFO_EXTENSION); try { header("Content-Type: image/$file_format"); header("Content-disposition: filename=image.$file_format"); $img = file_get_contents($url); echo $img; } catch(Exception $e) { echo $e->getMessage(); } } else die('Unknown request'); ?> A typical request would look like this: fetch_image.php?url=http://example.com/images/image.png Everything works fine on my local server but

I am struggling with a strange problem since I'm on production on a mutualized server. I have a firewall securing my admin panel matching all the url with /admin/*. On this administration panel, all the POST data that I send do not arrive to the controller. var_dump($this->get('request')->request->all()) gives me an empty array , same thing for : var_dump($_POST) This is very annoying since all my forms and CRUD functionalities do not work anymore... The other pages of my website (not on the admin panel) do work correctly. The Chrome and FireBug console show me that the data is sent the right

I'm trying to nest some routes under the namespace, account. I want user management under account like /account/users and /account/users/5/edit In routes.rb: namespace :account do resources :users do member do put 'generate_api_key' end collection do post 'api_key' end end end My controllers are not namespaced or put them in any different directory. /app /controllers accounts_controller.rb users_controller.rb In my development environment this is working fine, but in production I get 404 responses to any of the /account/users... paths (which, by the way, are all still generated correctly: new

I get the following error when I run my Rails application in production mode, but when I run my app in development mode it works fine. Can I use any gems in production mode? `require': No such file to load -- test_helper (LoadError) The following is the full trace of the code: /home/nyros/.rvm/gems/ruby-2.2.0@dfl/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `require': No such file to load -- test_helper (LoadError) from /home/nyros/.rvm/gems/ruby-2.2.0@dfl/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require' from /home/nyros/.rvm/gems/ruby

In Grunt or Gulp, I used to define all the requirements myself, like: stuff should be minified only for production, livereload should be enabled only in dev server. Webpack handles this on its own, via its -d and -p options , that toggle the loaders' minimize mode (most loaders ship with their relevant minifiers), the devtool and similar stuff (I don't know what exactly). Most of that "just works". But on the other hand, there are some libraries that have a development and production mode. For example, React looks at process.NODE_ENV , and if it's production , it disables the propTypes

We are currently using postgresql for our production database in rails, great database, but I am building the new version of our application around SQLite. Indeed, we don't use advanced functions of postgres like full text search or PL/SQL. Considering SQLite, I love the idea to move the database playing with just one file, its simple integration in a server and in Rails, and the performance seems really good -> Benchmark Our application's traffic is relatively high, we got something like 1 200 000 views/day. So, we make a lot of read from the database, but we make a few writes. What do you

ng build --prod Angular CLI command produces highly compressed javascript files in Angular4 application. When the application is ejected using ng eject command, Angular CLI commands are gone and we are left with npm scripts( npm run build command to build the app), but unfortunately that command outputs a non-production build. I tried running webpack -p command directly but the output result files are slightly larger compared to the output of ng build --prod command. How to get a compression equivalent of ng build --prod command but on an ejected application? What command/arguments can produce