Add next 5 upcoming meet_ups#11
Conversation
…o show upcoming meet ups TODO: add a valid API_KEY to server.js INFO: start page with > node server.js
…outs are in views
|
Hi @codingCookie ! Very cool of you to donate your time and energy to jumping in on our issue queue. This implementation looks great, there are just a couple things I'd like for us to consider before taking steps to converting this project into a node app. First, the current site is hosted on GitHub Pages, which is (as you most likely know) a free service that builds and deploys whenever you push a static site (or Jekyll project) to the The other consideration is cost of hosting. I know that at one point there were a few free services, but many of these seem to have transitioned away from offering a free tier. Do you know of any? I noticed your initial attempt was using Fetch - it would be nice to figure out a fix for the CORS issue since that seems to always cause trouble and having a reliable pattern would be nice as Fetch is only going to become more commonly used. Note, since IE still has no support whatsoever, you'll likely have to use a polyfill. One last thing - I think this is really cool and I really appreciate your contribution. It makes sense that a NodeSchool website would be hosted as a Node app. Thank you! |
connects to #8
I grabed the issue because i haven't done anything yet with the meetupAPI - and i like nodeschool :)
First i tried to get the events via an JS Fetch command - but i run into 'Allow-Origin'-problems.
My second idea was to use an express-server to get everything on the server - and not the client - and yay it works :) The only disadvantage is that you have to add an API_Key from meetUp (http://www.meetup.com/de-DE/meetup_api/auth/#keysign) - I had no idea how to hide it :/
Maybe you have one?
I hope you like my idea and implementation.
++ package.json, express & handlebars-template-engine to show upcoming meet_up's
TODO: add a valid API_KEY to server.js
INFO: start with > node server.js