Comments on: How To: Local Facebook App Development

By: How to Develop a Facebook App on Your Local Server using SSH « André Pareis

How to Develop a Facebook App on Your Local Server using SSH « André Pareis — Thu, 09 Jun 2011 23:39:39 +0000

[...] local development environment usually includes some network setup, for instance as described here: http://www.insidefacebook.com/2007/07/16/how-to-local-facebook-app-development/ However, I find these router and network setup design troublesome and I also want something that is [...]

By: Set up a remote forwaring port to develop Facebook apps locally « Ramblings

Set up a remote forwaring port to develop Facebook apps locally « Ramblings — Tue, 15 Apr 2008 20:36:53 +0000

[...] though. I hadn’t done remote port forwarding before but in starting to look for a solution, a comment on a post here said what I wanted to here. “Avoid the port-forwarding/NAT traversal/firewall [...]

By: Will

Will — Wed, 22 Aug 2007 00:53:28 +0000

Hi, thanks for the tutorial. It would be helpful if you could mention downloading the facebook library and where to install it within WAMP. The facebook site doesn’t explain it either at least for WAMP installs.

By: july link overload! « Vinu’s Online Cloud

july link overload! « Vinu’s Online Cloud — Thu, 09 Aug 2007 07:21:08 +0000

[...] Inside Facebook » How To: Local Facebook App Development [...]

By: Jonathan Lipps

Jonathan Lipps — Sun, 22 Jul 2007 21:52:46 +0000

Good tip, Larry. Losing the config data would be bad, indeed. For developers who don’t want to build a push script, however (if for example this would be the only aspect of the dev cycle requiring a push script as opposed to simple version control), it could be a bit cumbersome. I’m interested if there are any other solutions?

By: Larry Rubin

Larry Rubin — Sat, 21 Jul 2007 16:58:25 +0000

Great article Jonathan. This post and the others on your site are extremely informative and timely.

One quick note about custom configuration files and the build and release process-

In most cases you probably do want to track the revision history of your environment configuration files in source control- especially if those files are lengthy or difficult to reconstruct (as they usually are). That way you’ve got a known good copy in the event your live config goes bad or gets accidentally deleted.

I usually have a unique configuration file for each environment, and use a build script with a target of QA, PROD, etc. to tell the script which config file to push. This can be refined further by adding arguments of “code”, “config”, or “code+config”, in order to leave things alone that haven’t changed.

Keep up the excellent reporting! :)

Cheers.

By: Keith Hanson

Keith Hanson — Thu, 19 Jul 2007 16:45:47 +0000

Or you could just switch to Rails or Merb and Ruby and just use Capistrano for your pain free deployment. *grin*

By: sideshow bob

sideshow bob — Tue, 17 Jul 2007 00:54:16 +0000

You can avoid the port-forwarding/NAT traversal/firewall morass with some SSH hax:

http://blog.evanweaver.com/articles/2007/07/13/developing-a-facebook-app-locally