If you have your code defined in classes in lib/ folder you may have problems to load that code in production.
Autoloading is disabled in the production environment by default because of thread safety.
Change config/application.rb:
config.autoload_paths << Rails.root.join("lib")
config.eager_load_paths << Rails.root.join("lib")
NOTE: This post now lives (and kept up to date) on my blog: http://hakunin.com/rails3-load-paths
Do nothing. All files in this dir are eager loaded in production and lazy loaded in development by default.
| # (concern) e.g. for Post model | |
| module UserTrackable | |
| extend ActiveSupport::Concern | |
| included do | |
| before_create :set_created_by | |
| before_save :set_updated_by | |
| belongs_to :created_by, class_name: 'User', foreign_key: 'created_by_id' |
This is a sample script for uploading files to Google Drive using Javascript. The files are uploaded by Drive API v3. gapi.client.drive.files.create() can create an empty file on Google Drive. But it cannot directly upload files including contents. I think that this might not be able to upload files and metadata with the multipart/related, although this might be resolved by the future update. So now, as one of workarounds, I use using XMLHttpRequest.
In this sample script, a text file including contents is created under a folder.
| function arrayToCSV (twoDiArray) { | |
| // Modified from: http://stackoverflow.com/questions/17836273/ | |
| // export-javascript-data-to-csv-file-without-server-interaction | |
| var csvRows = []; | |
| for (var i = 0; i < twoDiArray.length; ++i) { | |
| for (var j = 0; j < twoDiArray[i].length; ++j) { | |
| twoDiArray[i][j] = '\"' + twoDiArray[i][j] + '\"'; // Handle elements that contain commas | |
| } | |
| csvRows.push(twoDiArray[i].join(',')); | |
| } |
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
If you’re new to building API’s with Rails you’ve probably wondered how to authenticate requests made to the API to ensure that they are coming from the correct source with correct permissions. Since API’s are stateless applications they do not have the ability to create sessions for users. (Read about how Rails Sessions work here) This creates some challenges when trying to handle authentication because the app isn’t able to remember a user’s session data from one request to the next.
Enter Json Web Tokens. Json Web Tokens (JWT) are a self contained authentication method designed for stateless authentication. A self contained authentication method is one that does not require any storage on the back-end to verify the authenticity of the request. All of the data necessary to authenticate the request is contained right inside the token!
| require 'headless' | |
| require 'capybara' | |
| require 'capybara/dsl' | |
| require 'selenium-webdriver' | |
| class EcommerceScrap | |
| include Capybara::DSL | |
| def initialize |
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm