Software At Robopartans @sfrbp - Tumblr Blog

Dynamic user field (EAV) in a Rails application (FLLCasts)

At FLLCasts.com we have new user attributes that we could create dynamically.

Search more for EAV and the many pros and cons of using it. It is one of those subjects software architects (like us) like to discuss over a beer. (Well this and entropy)

Just wanted to share that we've started using hydra_attribute and we are rather please with the results.

The attributes are added with a db migration:

class AddHydraAttributesToUser < ActiveRecord::Migration def up User.hydra_attributes.create({name: 'need_for_team_mentoring', backend_type: 'boolean', default_value: false, white_list: true}) ... end def down User.hydra_attributes.delete 'need_for_team_mentoring' ... end end

and the ui is pretty simple:

<li><%= f.check_box :need_for_team_mentoring %><%= f.label "Mentoring a team", :class => "checkbox inline"%></li>

Now the difficult part comes - how to make users actually fill this profile fields.

#ruby on rails #db

Ofcourse it is invalid - this Token

There is a moment in software development where you just start laughing and waiting for some signs from the "god of computers". I have been there, you have been there, it make us all feel very unhappy and its just wrong.

Below is the error from a Google OAuth2. Come on, can't you be just a little be more specific.

It turns out that you only get the refresh_token from Google on first authorization, then you are left with the access_token which expires unknown when and after expiration you can use it.

Would have been great if the message return was a little be more informative. Would have saved tens of minutes on thousands of developers.

Check out http://stackoverflow.com/questions/10827920/google-oauth-refresh-token-is-not-being-received

Completed 500 Internal Server Error in 100ms OAuth2::Error - <HTML> <HEAD> <TITLE>Token invalid</TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF" TEXT="#000000"> <H1>Token invalid</H1> <H2>Error 401</H2> </BODY> </HTML> : oauth2 (0.9.4) lib/oauth2/client.rb:113:in `request' oauth2 (0.9.4) lib/oauth2/access_token.rb:107:in `request' oauth2 (0.9.4) lib/oauth2/access_token.rb:114:in `get' () home/kireto/.rvm/gems/ruby-2.1.1/bundler/gems/youtube_it-42317b42fa59/lib/youtube_it/client.rb:523:in `current_user' () home/kireto/.rvm/gems/ruby-2.1.1/bundler/gems/youtube_it-42317b42fa59/lib/youtube_it/client.rb:538:in `client' () home/kireto/.rvm/gems/ruby-2.1.1/bundler/gems/youtube_it-42317b42fa59/lib/youtube_it/client.rb:141:in `upload_token' app/controllers/videos_controller.rb:30:in `get_upload_token'

#google #oauth2 #ruby on rails

YouTubeIt::AuthenticationError - A developer key is required for this operation:

Now that was awful. Most of the information on the internet is outdated. Google has changed their developers console.

The answer is that you should create a new

Public API Access and use the API key as the developers key

#google #oauth2 #youtube #api

"Access not configured" for Google OAuth2

You are not a true warrior until you fight a dragon.

You are also not a true developer until you fight oauth2 authorizations.

Below is the error I was getting and it seems I only have to authorize

Google+ API

Contact API

from the developers console. Took me a while to figure that out.

I, [2014-12-28T14:56:21.410473 #6279] INFO -- omniauth: (google_oauth2) Callback phase initiated. E, [2014-12-28T14:56:21.862503 #6279] ERROR -- omniauth: (google_oauth2) Authentication failure! invalid_credentials: OAuth2::Error, {"errors"=>[{"domain"=>"usageLimits", "reason"=>"accessNotConfigured", "message"=>"Access Not Configured. The API is not enabled for your project, or there is a per-IP or per-Referer restriction configured on your API key and the request does not match these restrictions. Please use the Google Developers Console to update your configuration.", "extendedHelp"=>"https://console.developers.google.com"}], "code"=>403, "message"=>"Access Not Configured. The API is not enabled for your project, or there is a per-IP or per-Referer restriction configured on your API key and the request does not match these restrictions. Please use the Google Developers Console to update your configuration."}: { "error": { "errors": [ { "domain": "usageLimits", "reason": "accessNotConfigured", "message": "Access Not Configured. The API is not enabled for your project, or there is a per-IP or per-Referer restriction configured on your API key and the request does not match these restrictions. Please use the Google Developers Console to update your configuration.", "extendedHelp": "https://console.developers.google.com" } ], "code": 403, "message": "Access Not Configured. The API is not enabled for your project, or there is a per-IP or per-Referer restriction configured on your API key and the request does not match these restrictions. Please use the Google Developers Console to update your configuration." } }

#google #oauth2

Ruby 2.2.0 is released...lets see when will it show in rvm

If you do

rvm list known

you get a list of all known rubies.

Lets see how long will it take to see this in

1. RVM

2. sudo apt-get install for ubuntu

I am planning on counting the actual days

#ubuntu #ruby #rvm

Backup heroru db with jenkins

When we are doing IT Due Diligence on projects we ask one important question:

How fast can you recover after lose of information?

In our www.fllcasts.com project we backup the production db on every build from jenkins with the following script:

curl -o production_backup$(date +"%Y_%m_%d")_$BUILD_NUMBER.sql.gz `heroku pgbackups:url --app the_heroku_app`

What is important is that in this way we have the db before each build and the produce file has date and BUILD_NUMBER.

The next questions is when do you delete this backups, but that's another question.

Use it in you project to never loose, and never fail an IT Due Diligence.

#ruby #jenkins #ruby on rails #due diligence

kirilmitov

Open source projects Die Hard

sfrbp

There is a good movie for this time of the year - it is called Die Hard and I just got reminded about it when I heard that the very popular “cancan” project in the rails community is dead.

Luckily, open source project Die Hard, especially the good once. The community has taken over with the CanCanCommunity - cancancan - http://thechangelog.com/cancancan/

What a great story.

#open source #ruby #ruby on rails

kirilmitov

couldn't find file 'jquery.ui.core'

sfrbp

Still migrating from RSpec2 to Rspec3 and the following error occurs:

couldn’t find file ‘jquery.ui.core’

This one would be tough. I am sure..

More than 20-30 minutes on this and still no answer.

I just fixed the working versions and will fight with this at another time:

gem “jquery-rails”, “3.1.0” gem “jquery-ui-rails”, “4.2.1”

#ruby #ruby on rails #jquery #rspec

kirilmitov

sfrbp

Now that’s a result:

227 examples, 131 failures, 19 pending

Lest see what is happening. Last error is:

undefined local variable or method `controller’ for #<RSpec::ExampleGroups::SubtitlesNewHtmlErb:0x0000000ae0d1c0>

Seems you can not mock controllers in the same way as in RSpec2.

...

#ruby #ruby on rails #rspec

kirilmitov

`mock_model` is deprecated

Continuing with migrating from RSpec2 to Rspec3 and this happens.

`mock_model` is deprecated. Use the `rspec-activemodel-mocks` gem instead.

Lets find a way to migrate it.

Add this to your gemfile:

gem ‘rspec-activemodel-mocks’

bundle

Still an error. I will give up on this and directly move from rspec 2.99 to 3.*. Don`t want to waste more time here. Lets see how this goes.

#ruby #ruby on rails #rspec

Upgrading RSpec2 to RSpec3 - step 8 from the official guide

This time the error is:

$ transpec /home/kireto/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/rubygems/specification.rb:2052:in `raise_if_conflicts': can't activate json-1.7.7, already activated json-1.8.1 (Gem::LoadError)

Oh, we kind of hate and love it in the same time. How should we proceed?

Add transpec to your Gemfile and run:

bundle install

bundle exec transpec

Next step returns and error

bundle exec transpec The current Git repository is not clean. Aborting.

So you set --force option

bundle exec transpec --force

and you finally get to :

Copying project for dynamic analysis...

#ruby #ruby on rails #rspec #transpec

Updating RSpec2 to RSpec3 - the path of the official guide

The official instructions seem long with about 13 steps - https://relishapp.com/rspec/docs/upgrade

But I decided to give it a try and the first error occurred on the second step:

You have requested: rspec = 2.99 The bundle currently has rspec locked at 2.14.1. Try running `bundle update rspec`

How do you solve this? Next thing you should do is:

gem install rspec -v 2.99

And then

rm Gemfile.lock

bundle install

At this stage you are passed step 2 from the official guide.

#ruby #ruby on rails #rspec

Setting Jenkins to use correct ruby version from RVM

Wont go into details, but on our staging & build machine there is ruby installed both from the Ubuntu apt-get and from RVM.

Question is - if your build job requires a ruby from RVM, how do you choose it.

Answer is - you set the ruby directly in the "executed shell script" from jenkins.

#!/bin/bash # Use the correct ruby source "$HOME/.rvm/scripts/rvm" rvm use "ruby-2.1.1" # Set "fail on error" in bash set -e

Don't forget

source "$HOME/.rvm/scripts/rvm"

#ruby #jenkins #ruby on rails

Migrating from Ruby 1.9.3 to Ruby 2.1.1

We did the migration on development, staging and production servers.

On development it was pretty easy since RVM was already installed.

rvm list known

rvm install ruby-2.1.1

and we were done.

One of the production servers is Heroku and again it was easy. Heroku chooses ruby based on the gemfile.

Most difficult it was on the staging & build server, because no RVM was installed.

Lessons learned again and again - try to keep your staging and build servers as close as possible to your development machines

#ruby #rvm #ruby on rails

Trending Blogs

Recently Viewed Blogs

Software At Robopartans