Sidekiq jobs can be enqueued or scheduled. Enqueued means that they are gonna be picked up as soon as possible, scheduled jobs will be enqueued at some specific time.
When using ActiveJobs, Rails will return a job_id after sending the job to ActiveJobs
job = UserMailer.send_invite(params).deliver_later
This list is based on aliases_spec.rb.
You can see also Module: RSpec::Matchers API.
| matcher | aliased to | description |
|---|---|---|
| a_truthy_value | be_truthy | a truthy value |
| a_falsey_value | be_falsey | a falsey value |
| be_falsy | be_falsey | be falsy |
| a_falsy_value | be_falsey | a falsy value |
Command Line
pry -r ./config/app_init_file.rb - load your app into a pry session (look at the file loaded by config.ru)pry -r ./config/environment.rb - load your rails into a pry sessionDebugger
| #!/bin/sh | |
| #TODO: add exclude <file>.rb in rubocop.yml ? | |
| git status --porcelain | egrep "^(A|AM|^M).+\.rb$" | awk '{print $NF}' | xargs rubocop -a |
| #!/bin/bash | |
| # This attempts to concurrently execute an AWS Lambda function. WIP. | |
| # After execution, roughly NUM_EXECUTION containers will be ready | |
| # to accept requests. | |
| # More advanced strategies are out there. Check out @lambdacult on twitter, for example. | |
| AWS_LAMBDA_FUNCTION_NAME=LambdaInfo | |
| NUM_EXECUTIONS=3 |
It seems that it does not matter what timezone is on the server as long as you have the time set right for the current timezone, know the timezone of the datetime columns that you store, and are aware of the issues with daylight savings time.
On the other hand if you have control of the timezones of the servers you work with then you can have everything set to UTC internally and never worry about timezones and DST.
Here are some notes I collected of how to work with timezones as a form of cheatsheet for myself and others which might influence what timezone the person will choose for his/her server and how he/she will store date and time.
| #!/bin/bash | |
| # Caddy daemon | |
| # chkconfig: 345 20 80 | |
| # description: Caddy daemon | |
| # processname: caddy | |
| DAEMON_PATH="/usr/local/bin" | |
| DAEMON='./caddy' | |
| DAEMONOPTS="-conf=/etc/caddy/Caddyfile -log /var/log/caddy.log" |
Look at LSB init scripts for more information.
Copy to /etc/init.d:
# replace "$YOUR_SERVICE_NAME" with your service's name (whenever it's not enough obvious)
| $ mysqld_safe --bind-address=127.0.0.1 --data-dir=/usr/local/var/mysql --skip-grant-tables --user=root |