5 ms·
How it worked last year: - Internet: We had 3 Sprint wifi hotspots on the bus. You could connect to any of them, but if one started to get overloaded it defini
by shiftb 16y ago
How it worked last year:
- Internet: We had 3 Sprint wifi hotspots on the bus. You could connect to any of them, but if one started to get overloaded it definitely slowed down. California, Arizona, and Texas were fine, but Sprint seems to be unaware of New Mexico's existence. I had a Verizon Palm Pre and I used the mobile hotspot a lot. I know a couple others did similar things.
- Server: We didn't have an on-bus server. The internet was reliable enough to download things like jquery locally and do all the dev locally. Since my team used git we had an easy time pushing and pulling code from each other even when the internet was spotty. A couple of us are thinking about donating a laptop to run as an onboard server/git repo.
- imrehg 16y agoThat sounds great, looking at my own questions I'm probably overcomplicating things and wouldn't know it well what works until I tried for real. Or maybe it is all part of the StartupBus idea - work with the given constraints. :) I wonder how much of the requirements are specific to this situation, or one could put together a mobile-productivity-bundle: some hardware + software to deploy similar environment anywhere on a short notice. :) Loved the idea of auto-geotagged blog posts that was mentioned on the site, I think. Any chance of sharing it? :)
- shiftb 16y agoI think you're right. It wasn't perfect, but it was good enough. :) And the constraints forced everyone to focus on only what needed to get done. I think we can share it. We'll probably open source the map component. We're rebuilding it this week, if you're inclined to help with that let me know. :)
- imrehg 16y agoSure! I've sent you an email. :)