bike_index
Joined 12 years ago
Joined 12 years ago
I would also love to hear a cost benefit analysis a year into managing your own servers.
It's all the ease of Heroku and all the flexibility of actual servers, and way cheaper than Heroku. The only reason I've touched Docker on Cloud66 is JRuby - since this article is about a python app, it would be also require Docker. But for Ruby MRI applications, the logical first step as soon as Heroku stops being cost effective is immediate (and painless) migration to Cloud66.
Initially we considered Apiary, but we wanted more flexibility and preferred to host things ourselves. And the fact that our documentation is generated automatically from the code via grape-swagger is a game changer.
My bike is fast and convenient for getting around, which makes it a reasonable alternative to other transportation methods (it's faster than traveling by car within the city limits of Chicago).
In contrast, a ~100$ bike is much slower and more expensive to maintain. Suggesting only fools ride nice bikes is short sighted.
We need to make bike theft less profitable instead of telling everyone to ride shitty, impractical bikes.
[1] in Chicago - http://www.transitchicago.com/travel_information/fares/unlim...
We've successfully recovered thousands of bikes (three in the past two days!). We've made it easy to id stolen bikes, and more difficult to sell stolen bikes - which makes ultimately bike theft less appealing.
GPS trackers are great - but unfortunately, they have yet to meet these vital requirements: easy to charge, difficult to remove, waterproof, cheap enough to put on everyone's bikes.
Here's another article about what to do if your bike is stolen - https://medium.com/@stolenbikessfo/what-to-do-after-you-bike...
Selling users isn't the only way to make money.