I was invited by Shopify to come and visit Ottawa for 3 Weeks while having a job-application there.
My homebase is the Les Suites Hotel in the city center.
It's the perfekt location to explore Ottawa, as it's close to the Byward Market, Ottawa River and the Rideau Canal.
I attached a couple of photos with dropbox.
| # (create oauth2 tokens from Google Console) | |
| client_id = "" | |
| client_secret = "" | |
| # (paste the scope of the service you want here) | |
| # e.g.: https://www.googleapis.com/auth/gan | |
| scope = "" | |
| client = OAuth2::Client.new(API_CLIENT, API_SECRET, { | |
| :authorize_url => 'https://accounts.google.com/o/oauth2/auth', | |
| :token_url => 'https://accounts.google.com/o/oauth2/token', | |
| # Set options that get passed on to Faraday | |
| :connection_opts => {:proxy => { :uri => 'http://127.0.0.1:8888'} }, | |
| :ssl => {:verify => false} | |
| }) |
| = Ruby Packaging Standard | |
| The aim of this document is two-fold. First, to specify a common | |
| structure of how a Ruby package distributed as source (that is, but | |
| not limited to, development directories, version-controlled | |
| repositories, .tar.gz, Gems, ...) should conform to. | |
| Second, to document common and proven ways to structure Ruby packages, | |
| and to point out certain anti-patterns that sneaked into common use. | |
| It is by intent not to innovate. |
| require 'rubygems' | |
| require 'eventmachine' | |
| ### EM::run takes over the process | |
| # puts 1 | |
| # EM.run{ | |
| # require 'mycode' | |
| # } | |
| # puts 3 # this will never happen |
| def make_sandwiches(however_many) | |
| sandwiches = [] | |
| however_many.times do | |
| sandwiches << make_sandwich { |sandwich| yield sandwich } | |
| end | |
| sandwiches | |
| end | |
| def make_sandwich | |
| puts "makin a sandwich" |