In some of the examples that use OAuth, the tokens are things like GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET. var params = { code: code, client_id: 'GOOGLE_CLIENT_ID', client_secret: 'GOOGLE_CLIENT_SECRET', redirect_uri: callbackURL, grant_type: 'authorization_code' }; Are these replaced somehow with real values? Where does that happen?
They are replaced with real values on a proxy server, outside of the node.js process.
Runnable – Edit, run, and share code in your browser
31–40 of 60 posts
Re: Runnable – Edit, run, and share code in your browser
#32Re: Runnable – Edit, run, and share code in your browser
#33Re: Runnable – Edit, run, and share code in your browser
#34Re: Runnable – Edit, run, and share code in your browser
#35Is this javascript only?
Re: Runnable – Edit, run, and share code in your browser
#36Seems awfully similar to http://webshell.io/
Re: Runnable – Edit, run, and share code in your browser
#37I want to sign in with GitHub and see my projects run.
Re: Runnable – Edit, run, and share code in your browser
#38At the risk of giving away a million dollar idea; nobody's gonna wanna really edit things in the browser. Too risky and missing features of whatever their favorite editor is. But how about letting people push their code up via git? So you could have a runnable browser window open, push your changes up to your runnable repo and then hit run? If this does turn out to be the key that breaks this open please remember it…
Here's another idea. JSBin is doing something pretty awesome: it uses the HTML5 File API so that you can select a file from your computer and it syncs to different instances of the same bin while you edit it in your favorite editor. Check it out: http://www.youtube.com/watch?v=mY56fNmn2cE (keep in mind the video was taken during development, now it's pretty stable). BTW some people like editing in the browser and tha…
Re: Runnable – Edit, run, and share code in your browser
#39and it's dead.. means it's not ready for hacker news invasion =))))