ruby - cron job generated by whenever/capistrano for a Sinatra app sets the wrong environment variable -


i using whenever gem in sinatra app create cron job. using whenever/capistrano job created/updated on deploy. whenever setup of deploy script:

require 'whenever/capistrano' set :environment_variable, 'rack_env' set :whenever_roles,        ->{ :app } set :whenever_command,      ->{ [:bundle, :exec, :whenever] } set :whenever_command_environment_variables, ->{ { rack_env: fetch(:whenever_environment), rails_env: nil } } set :whenever_identifier,   ->{ "#{fetch(:application)}_#{fetch(:stage)}" } set :whenever_environment,  ->{ fetch :rack_env, fetch(:stage, "production") } set :whenever_variables,    ->{ "environment=#{fetch :whenever_environment}" } set :whenever_update_flags, ->{ "--update-crontab #{fetch :whenever_identifier} --set #{fetch :whenever_variables}" } set :whenever_clear_flags,  ->{ "--clear-crontab #{fetch :whenever_identifier}" }

when deploy, can see capistrano runs crontab update , seems proper environment variable going used:

info [8b4f49a6] running ~/.rvm/bin/rvm default bundle exec whenever --update-crontab sidekiq-monitor-ua_staging --set environment=staging --roles=app deploy@10.0.254.37 debug [8b4f49a6] command: cd /var/www/sidekiq-monitor-ua/releases/20160725170122 && ( rack_env=staging rails_env= ~/.rvm/bin/rvm default bundle exec whenever --update-crontab sidekiq-monitor-ua_staging --set environment=staging --roles=app ) debug [8b4f49a6]        [write] crontab file updated

however, in crontab (this generated deploying staging environment):

# begin whenever generated tasks for: sidekiq-monitor-ua_staging 0,5,10,15,20,25,30,35,40,45,50,55 * * * * /bin/bash -l -c 'cd /var/www/sidekiq-monitor-ua/releases/20160725170122 && rails_env=staging bundle exec rake log_sidekiq_status --silent >> /dev/null 2>&1'  # end whenever generated tasks for: sidekiq-monitor-ua_staging

consequently, when crontab runs rake task, rack_env not set , code doesn't run because defaults development environment.

i either missing or have misconfigured. hope can help.

the environment_variable mentioned in whenever github readme job types: https://github.com/javan/whenever#define-your-own-job-types

the default rake job here

job_type :rake, "cd :path && :environment_variable=:environment bundle exec rake :task --silent :output" job_type :runner, "cd :path && bin/rails runner -e :environment ':task' :output"

:environment_variable default 'rails_env'

you can try below.

require 'whenever/capistrano' set :environment_variable, 'rack_env' set :whenever_roles,        ->{ :app } set :whenever_command,      ->{ [:bundle, :exec, :whenever] } set :whenever_command_environment_variables, ->{ {} } set :whenever_identifier,   ->{ "#{fetch(:application)}_#{fetch(:stage)}" } set :whenever_environment,  ->{ fetch :rack_env, fetch(:stage, "production") } set :whenever_variables,    ->{ "'environment=#{fetch :whenever_environment}&environment_variable=rack_env'" } set :whenever_update_flags, ->{ "--update-crontab #{fetch :whenever_identifier} --set #{fetch :whenever_variables}" } set :whenever_clear_flags,  ->{ "--clear-crontab #{fetch :whenever_identifier}" }

Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more