production

I finally released my project to the production level and suddenly I have some issues I never had to deal with in the development phase. When the users posts some actions, I sometimes get the following error. Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File "home/ubuntu/server/opineer/comments/views.py", line 103, in comment_expand comment = Comment.objects.get(pk=comment_id) File "/usr/local/lib/python2.7/dist-packages/django/db/models

Starting a new project. It's basically a blogging/commenting system. We're considering node.js as the back end server. Is node.js ready for this sort of thing or is it too early and experimental? We need HTTPS and gzip compression - perhaps a front end nginx server could provide this? What's missing from node.js that would make developing a web app difficult? From a production ready perspective, we're wondering if it is stable enough for building a commercial app on top of. Thanks selfawaresoup UPDATE: Almost a year has passed and now I'd definitely use node.js for live systems. It's not ready

I would like to view some variables in controller, it tried the following: Rails.logger.debug "Year: #{Time.now.year}" puts "Year: #{Time.now.year}, Month: #{@month}" where can I see the output for Logger or Puts in production mode? Do I need so set something up to view these somewhere? The normal log level in production is info , so debug logs are not shown. Change your logging to Rails.logger.info "Year: #{Time.now.year}" to show it in production.log . Alternatively (but not a good idea) you can raise the logging level in /config/environments/production.rb : config.log_level = :debug Update

We are in the process of deploying a new application using play 2.1.1 to production and are having some real issues with it and the very limited documentation didn't help much... So it was time to update to a new version, we ran our usual stop/upgrade/start scripts but they failed. For some reason, play was refusing to apply the evolutions. When starting it kept saying Oops, cannot start the server. @6elnj89fh: Database 'default' needs evolution! This was even though we tried setting applyEvolutions.default=true both through command line and in the application_prod.conf file. It also

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 => 'xxxxxx.com', :authentication => :plain, } config.action_mailer.default_url_options = { :host => 'localhost