If you want to cache an action, based on all the query parameters (or say on nearly all of them), you can do: caches_action :my_action, :cache_path => Proc.new { |c| c.params } Or, maybe you want all but some params that you just use for Analytics (but that have no bearing on the records you’re … Read more
I agree with your idea to use an Achievement model. You should probably not implement the triggers in your controllers, though. Imagine that you have two ways to post a comment; you will inevitably get code duplication. This sort of behaviour belongs in a model. Suppose you want to track the number of comments that … Read more
TLDR: Use environment variables! I think @Bryce’s comment offers an answer, which I’ll just flush out. It seems one approach Heroku recommends is to use environment variables to store sensitive information (API key strings, database passwords). So survey your code and see in which you have sensitive data. Then create environment variables (in your .bashrc … Read more
If you want all your links to be able to switch between http and https, you have to stop using the _path helper and switch to _url helpers. After that, using a scope with the protocol parameter forced and protocol constraint makes the urls automatically switch. routes.rb scope :protocol => ‘https://’, :constraints => { :protocol … Read more
Apparently ubuntu and ruby don’t always catch dependencies like they should. From the first google hit (yeah, I clicked on this stack-overflow in place #2 before checking out the first result.) Navigate to the Ruby source and enter: sudo apt-get install libreadline5-dev cd ext/readline ruby extconf.rb make sudo make install So, if you’re on another … Read more
At a high level, the intent of resource is to declare that only one of these resources will ever exist. For example: resource :profile, :only => [:edit, :update] As a user, I should only be able to update my own profile. I should never be able to edit other users’ profiles, so there’s no need … Read more
It’s now possible to try the Heroku feature Roberto wrote about in his answer, without contacting Heroku. It’s called Heroku Labs: Dyno Metadata and you can enable it by heroku labs:enable runtime-dyno-metadata -a <app name> and then the information is available (on the next deploy) as environment variables: ~ $ env HEROKU_APP_ID: 9daa2797-e49b-4624-932f-ec3f9688e3da HEROKU_APP_NAME: example-app … Read more
Don’t. If you’re looking for seed data, you should use db/seeds.rb and rake db:seed instead. More info in this Railscast. Side note: Always make sure that the code in db/seeds.rb is idempotent. i.e. It should always be safe to re-run your seeds. But, if you must insert or modify data inside a migration (there are … Read more
When testing locally your production environment, you have to compile the assets locally. Simply run the command below: RAILS_ENV=production bundle exec rake assets:precompile It will generate all the assets under public/assets. Next, you have to tell Rails to serve the assets itself. Server software (eg. Nginx or Apache) do it for you on environments like … Read more
I think you’ll need to manage the Devise views yourself. Try the following in a console: rails generate devise:views This will generate all the views Devise uses (including mailer templates), which you can now customize. The mailers you’re looking for should then be in ‘app/views/devise/mailer’ If you want to generate scoped views, or only a … Read more