Import codebase from thoughtbot

[croaky]

Remove things like KISSMetrics, New Relic, accounts, subscriptions, plans, limits.

[croaky]

I began ripping out the thoughtbot-specific code tonight. Things like KISSMetrics, Tender, email/password authentication, accounts, plans, limits, billing, Braintree, terms of service, privacy policy, contact page, email delivery, Google Analytics, Heroku, Airbrake, announcements, A/B testing, and New Relic are now gone.

I'll need to return to it Wednesday night to spend some more time fixing up the tests and some of the new user interface flows. I'm hoping to move the code into this repo by the end of the week.

[kareemk]

@croaky sounds good although i imagine some of these services you're removing most people will want to run in their production environments. are you envisioning that everyone will have to fork the project to configure for their specific environment?

[croaky]

I think the only ones that people might want are Heroku, Airbrake, and New Relic. I'd rather not force people to decide to use them and let them pick and choose. All are super-simple to set up oneself.

[patricksrobertson]

Agreed on configuration of Airbrake and New Relic on Heroku.

@croaky have you made any progress on the preparation lately?

I understand this is less than glamorous work but at the same time I'd like have a couple of iterations before the shutdown to setup a staging/production environment to minimize potential risk with the switchover. If that's not possible, I can plan to switch to a static version of the i18n keys we use until you feel good about the codebase.

[croaky]

I've got a version pushed here. I've removed things like private keys, plans/accounts/subscriptions/users/limits, KISSMetrics/New Relic/Airbrake. I also eliminated the Redis dependency to make it slightly easier and cheaper for people to run this on their own. It still requires a background worker via Delayed::Job.

The test suite is green under Ruby 1.9.2 and I successfully deployed it from scratch to Heroku's Cedar stack.

I aimed for utter simplicity as I was re-working the code to be open sourced so you'll notice the project drop-down / current_project concept is gone. I'd also like to go with HTTP Auth per-project to simplify user accounts / admins / permissions.

I'm going to create a few issues tomorrow night and re-work some of the user flows. Patrick, do you want to meet at the Boston Ruby hackfest at thoughtbot on Tuesday night to work on some things together?

[patricksrobertson]

Sounds like a plan @croaky.