Tag Info

New answers tagged

1

You need to set root in the server block, not in the location block. This is one of the most common nginx mistakes. In the location where you need to override the document root, use alias instead of root so that the path is translated properly.


0

For whoever runs into this problem in the future: It took me long but it's fixed. This is what I did: sudo apt-get purge imagemagick libmagickcore-dev libmagickwand-dev sudo rm -R /usr/include/ImageMagick-6/magick sudo ln -s /usr/lib/x86_64-linux-gnu/ImageMagick-6.8.9/bin-Q16/Magick-config /usr/bin/Magick-config sudo apt-get install imagemagick ...


0

From http://guides.rubyonrails.org/debugging_rails_applications.html#log-levels: The available log levels are: :debug, :info, :warn, :error, :fatal, and :unknown, corresponding to the log level numbers from 0 up to 5 respectively. To change the default log level, use config.log_level = :warn # In any environment initializer, or Rails.logger.level = ...


0

Is there a way to prevent this? Potentially, install & configure 'cpulimit' package if possible. Nice/renice might help. should you be concerned about this when you sign for a vps service? That TOS is ridiculous and puts burden of resource consumption monitoring on the user. Any other company will give you X resources and you are allowed (at least ...


2

The problem is simple. Magick-config is not found anywhere on your system. When you uninstalled imagemagick, it was also uninstalled - and apparently you didn't install it with imagemagick again. To solve this, install the following package: sudo apt-get install libmagick++-dev graphicsmagick-libmagick-dev-compat libmagickcore-dev Then rerun the gem ...


2

The operation of proxy_pass is explained in nginx documentation: http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass A request URI is passed to the server as follows: If the proxy_pass directive is specified with a URI, then when a request is passed to the server, the part of a normalized request URI matching the location is ...


0

Spot the differences between nginx: upstream app { server unix:/tmp/unicorn.myapp.sock fail_timeout=0; } And your unicorn configuration: listen "/tmp/unicorn.rails.sock" You should probably point both to the same socket...



Top 50 recent answers are included