4 ms·
I love simple solutions! It reminds me of a personal web site I built recently. I am climbing the 4000 footers of New Hampshire with my wife. It's a big challe
by thehappypm 8y ago
I love simple solutions!
It reminds me of a personal web site I built recently. I am climbing the 4000 footers of New Hampshire with my wife. It's a big challenge, to climb almost 50 of some of the biggest mountains east of the Mississippi, and a ton of fun for a weekend warrior couple.
We've been putting information into a spreadsheet to track our progress, and I decided it'd be fun to make a web site, where you can see the mountains we've done, the ones we haven't done, and see our trip reports and photos. I started queuing up a database and thinking about a UI to enter the hike data into, but then I realized: why not just use our google spreadsheet as the database, directly?
I did some research and you can set up a google sheet to be publicly available as a CSV. So when you access my web site, it simply downloads the CSV at that public URL, parses it, and uses it to power menus and individual hike report pages. When we finish another hike, we simply add another row (like we always had!), and the web site gets a new page made almost instantly. The code doesn't even authenticate with Google, since the data is public, and the whole thing runs pretty well!
- dhc02 8y agoThat's pretty cool. How long does it take to load a page with that setup?
- thehappypm 8y agoEach page takes a second to load usually, but it's a dopey Heroku web dyno, so it takes just about that long to load the landing page that doesn't go down that code path.
- kyleblarson 8y agoI lived on Mt Moosilauke for a summer back in the day.