jleo3

#! /usr/bin/env bash

set -o errexit

sudo apt-get update && sudo apt-get upgrade
install="sudo apt-get install -y -q"
update="sudo apt-get update -q"

# setup install directory
mkdir -p /tmp/install

jleo3

Maintain a web application that allows Rails developers to pessimistically version their Gemfiles.

Create a service that does what the pessimize gem does, only do it way better!

1. Allow authentication with GitHub.
2. Search the user's GitHub repository and list Rails projects with Gemfile and Gemfile.lock included.
3. Identify each Rails repo as "compliant" or "non-compliant" with versioning principles.
4. For any "non-compliant" Rails repo, create a changeset that will bring the Gemfile in compliance.

Examples

An Example with rails new

jleo3

Code Conductor Goals

These are the initial goals of the project and are meant to start very simple. We will create something small and useful, release, collect feedback, and repeat.

Maintain a web application that allows Rails developers to pessimistically version their Gemfiles.

1. Allow authentication with GitHub.
2. Search the user's GitHub repository and list Rails projects with Gemfile and Gemfile.lock included.
3. Identify each Rails repo as "compliant" or "non-compliant" with versioning principles.
4. For any "non-compliant" Rails repo, create a changeset that will bring the Gemfile in compliance.

Examples

jleo3

Web App

• From what I can gather, Go devs recommend us to "just use net/http," a library that ships with Go. Then, as new elements are needed (middleware, persistence, ORM), find and add the appropriate libraries. This is the equivalent of starting with the Rails router and building out from there.

• I like the minimalist approach, but I also know I'll need guidance. The folks at Square wrote about this and suggested using Gorilla packages as necessary. So this is how I'll proceed until I hit a roadblock. So far I've integrated the Gorilla mux package.

Templating

• I searched for haml and found a single un-maintained repository. It looks like folks are gravitating to ace and amber. I chose amber because it's modeled after haml, while ace is modeled after slim.

Testing

• I've looked at

jleo3

Terms

• SEO: Search engine optimization
• SEPR: Search engine page rank
  • how many entries show up before your site
  • also refers to the algorithm used to rank websites in their search engine results.
• SERP: Search engine results page
• SEA: Search engine advertising
  • making payment directly to a search engine for advertiesment.
• examples include sponsored links and pay-per-click (PPC) advertising

jleo3

• We can try a more actively maintained version of the same gem.
• We can use Enumberable#each_slice to break up the nodes array.
• We can try a totally different library.

jleo3

<!--When editing this file, please update this section to keep all users up to date: 

TEMPLATE  ACTION
x         Shorthand for "x => x."
ps        Shorthand for "protected static "
it        Start an "It" statement
est       Start an "Establish" statement
dis       Disable two warnings most often seen in Mspec files
bec       Start a "Because" statement
spec      Create a new Spec class

jleo3

<?xml version="1.0"?>
<User UserClass="urn:dece:role:user:class:<%= account_type %>" UserID="<%= user_id %>" xmlns="<%= xmlns %>">
  <Name>
    <GivenName><%= name %></GivenName>
    <SurName>Wavelength</SurName>
  </Name>
  <ContactInfo>
    <PrimaryEmail>
      <Value><%= email %></Value>
      <ConfirmationEndpoint><%= email %></ConfirmationEndpoint>

jleo3

ruby 2.1.2p95 warpaint in ~/dev/roughcut
± |feature/78124008 ✗| → heroku run rake vudu:parse_rss -r prod
Running `rake vudu:parse_rss` attached to terminal... up, run.5985
DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/Rakefile:12)
DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/Rakefile:12)
****

jleo3

###3rd Party API Comparisons

#### Plaid
- Uses APIs instead of screen-scraping. Because of this, their developers promise it will work much faster than services like Intuit or Yodlee.
- The fact that they "clean up" their transaction names is a problem for us. For example, the Wall Street Journal subscriptions appear simply as "Dow Jones."
- They are bound by the historical limitations placed on them by each financial institution. With Amex, we can get up to 2 years of history. However, a Chase credit card will only fetch us 3 months of history. More details [here](https://github.com/plaid/support/blob/master/data-availability.md).
- We might be able to collaborate with Plaid to improve their service. More on this below.
 
#### The Amex Gem