Gist 706255

100%

✓ Published0🌍 Public

Last edited Nov 19, 2010

Created on Nov 19, 2010

This example shows a server-side Ruby on Rails configuration that adjusts OmniAuth’s URL generation for production environments. It overrides the `full_host` method inside the `OmniAuth::Strategy` module to strip the path and query from the incoming request URL, force the port to 443 for HTTPS or 80 for HTTP, and return the cleaned absolute URI. The code uses Ruby’s `URI.parse` and the `request.url` helper to rebuild the host string. No data visualization is present; the snippet is purely an authentication-related code patch.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 182105

This example demonstrates how to configure the Passenger Apache module for a Ruby on Rails application, specifically showing the distinction between default and RVM-managed Ruby environments. The visualization presents the two configuration approaches side by side, highlighting the commented-out default passenger settings versus the active RVM-based paths. The code uses Apache’s `LoadModule` directive and `PassengerRoot`/`PassengerRuby` configuration directives from the passenger gem, sourced from DylanFM’s gist. The rendering approach is textual, displaying the raw configuration file content without any graphical libraries or data visualization APIs.

DDylanFM

64% match

Loading thumbnail…

Gist 182074

This example visualizes a short Apache configuration snippet from a gist, showing how a developer integrates Phusion Passenger with Ruby version management. The code demonstrates the use of `LoadModule` and `PassengerRuby` directives to switch between system Ruby and RVM-managed Ruby 1.8.6, with the data source being the gist’s raw text file. The visualization likely uses a text-based rendering approach, such as a syntax-highlighted code block, rather than a charting library, since the content is purely textual. No graphical libraries like `d3` or Three.js are employed; instead, the focus is on presenting the configuration lines as-is.

DDylanFM

64% match

Loading thumbnail…

Gist 525907

This Ruby code defines an OmniAuth strategy for authenticating users with Google via OAuth, then retrieves basic profile information from the Google Contacts feed. It uses the `omniauth/oauth` library and the `multi_json` gem to parse the JSON response from `http://www.google.com/m8/feeds/contacts/default/full?max-results=1&alt=json`. The strategy extracts the user’s email and name from the feed’s `id` and `author` fields, falling back to the email if the name is unknown. It overrides the request phase to include a scope parameter for the contacts feed.

XXXX

63% match

Loading thumbnail…

Gist 214440

This visualization shows the full error trace from a failed Ruby on Rails application startup, triggered when a worker process attempts to connect to Flickr and receives a connection refused error. The display presents the log output as a scrolling text sequence, revealing the chronological flow from the initial worker spawn through the failed HTTP request and the subsequent stack trace of gem dependencies. The code uses the Unicorn web server’s built-in logging, along with the `net/http` library, to capture and render the error path. The data originates from a gist file containing the raw textual log.

XXXX

59% match

Loading thumbnail…

Gist 357899

This example shows a server error trace from a Ruby Unicorn web server, rendered as a plain-text visualization of the crash stack. The display lists the failed file `gistfile1.txt` with its read error, followed by the sequential Ruby method calls leading to the failure, from `process_client` down through `worker_loop` and `spawn_missing_workers`. The code relies on the Unicorn HTTP server gem’s internal call stack, using Ruby’s default exception reporting to expose the call chain. No external visualization library is used; the output is simply the raw error text formatted as a list of stack frames.

XXXX

58% match

Loading thumbnail…

omniauth using google openid

This example shows a Sinatra application that authenticates users via Google’s OpenID provider, displaying a login button on the root route and a personalized welcome message on `/app` after successful sign-in. It uses the OmniAuth framework with the `omniauth-openid` adapter, configuring a filesystem-backed OpenID store and a `:google` provider with Google’s discovery identifier. The app handles the callback at `/auth/:name/callback` by extracting user info from the `omniauth.auth` request environment, storing a formatted name and email in Sinatra’s session (enabled via `enable :sessions`), and redirecting to the protected page. Logout clears the session and returns to the root.

TTBD

58% match

Loading thumbnail…

Gist 850654

This example shows how to test authorization and role-protected attribute updates in a Rails controller using RSpec. It verifies that a user cannot edit another user’s profile, can change their own given name, and cannot modify their role field, with assertions on flash messages, response codes, and assigned attributes. The code uses Devise::TestHelpers to sign in a factory-built user, and RSpec’s `describe`, `context`, and `it` blocks to structure the test cases.

VVortex

57% match

Loading thumbnail…

Gist 152205

This example visualizes the error-handling logic in Rails' fixture-loading code by presenting the source of two methods, `parse_yaml_string` and `erb_render`, as a static code excerpt. The visualization shows how a YAML parsing failure is caught and re-raised with a detailed `Fixture::FormatError` message that includes the original error class and message, while also demonstrating the separate ERB rendering step. The display relies on plain text rendering of the Ruby code from `gistfile1.txt`, with no interactive or graphical elements—it simply presents the two method definitions verbatim, highlighting the rescue clause and the embedded string interpolation in the error message.

XXXX

56% match