Aurélien Malisart
2008-Jun-19 09:46 UTC
[Facebooker-talk] facebook apps developement "process"
Hi everybody. New to facebook plateform and at the moment giving a try to Facebooker. I''ve developed a simple test app just to see how it works, and I''m wondering how you organize your work and deployment process. 1) When you''re developing. Do you commit/push with your favorite SCM tool each time you modify something just to see if it works or not (and debug)? Not very convenient... Or, do you use some tunneling-hack to send the requests to your local dev machine or something like this? 2) How do you deal with development/production apps? Do you register two apps on FB? I mean one for dev and one for production. And then switch between them? Thanks! aurels -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/facebooker-talk/attachments/20080619/e0142d95/attachment.html>
Aur?lien Malisart wrote: > 1) When you''re developing. > > Do you commit/push with your favorite SCM tool each time you modify > something just to see if it works or not (and debug)? > Not very convenient... Set the callback url to be http://localhost[:port]/ and the app will run off your machine, avoiding the need to commit just to test. If youre using FBML rather than iframe then localhost won''t work ... you''ll need to specify an externally accessible IP I think. That setup would imply that yes you would probably want to register a production and development (with the developer mode ticked) app on FB. HTH
Here''s a shameless plug: Check out Tunnlr: http://tunnlr.com It makes the tunneling hack effortless. That''s how we develop all of our applications. Mike On Jun 19, 2008, at 5:46 AM, Aur?lien Malisart wrote:> Hi everybody. New to facebook plateform and at the moment giving a > try to Facebooker. > > I''ve developed a simple test app just to see how it works, and I''m > wondering how you organize your work and deployment process. > > 1) When you''re developing. > > Do you commit/push with your favorite SCM tool each time you modify > something just to see if it works or not (and debug)? > Not very convenient... > > Or, do you use some tunneling-hack to send the requests to your > local dev machine or something like this? > > 2) How do you deal with development/production apps? > > Do you register two apps on FB? I mean one for dev and one for > production. And then switch between them? > > Thanks! > > aurels > _______________________________________________ > Facebooker-talk mailing list > Facebooker-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/facebooker-talk-- Mike Mangino http://www.elevatedrails.com
Joseph Sofaer
2008-Jun-19 18:16 UTC
[Facebooker-talk] facebook apps developement "process"
Aur?lien, Your other option is dynamic dns. So you can use a service like http://www.dyndns.com/services/dns/dyndns/ to get a url which they will route to you. You probably also have to set your router up to do port forwarding. So have port 3000 go to you computer''s ip. Then you want a development app, a production app and likely a staging app. Best, Joseph On Thu, Jun 19, 2008 at 4:54 AM, Mike Mangino <mmangino at elevatedrails.com> wrote:> Here''s a shameless plug: > > Check out Tunnlr: http://tunnlr.com > > It makes the tunneling hack effortless. That''s how we develop all of our > applications. > > Mike > > On Jun 19, 2008, at 5:46 AM, Aur?lien Malisart wrote: > >> Hi everybody. New to facebook plateform and at the moment giving a try to >> Facebooker. >> >> I''ve developed a simple test app just to see how it works, and I''m >> wondering how you organize your work and deployment process. >> >> 1) When you''re developing. >> >> Do you commit/push with your favorite SCM tool each time you modify >> something just to see if it works or not (and debug)? >> Not very convenient... >> >> Or, do you use some tunneling-hack to send the requests to your local dev >> machine or something like this? >> >> 2) How do you deal with development/production apps? >> >> Do you register two apps on FB? I mean one for dev and one for production. >> And then switch between them? >> >> Thanks! >> >> aurels >> _______________________________________________ >> Facebooker-talk mailing list >> Facebooker-talk at rubyforge.org >> http://rubyforge.org/mailman/listinfo/facebooker-talk > > -- > Mike Mangino > http://www.elevatedrails.com > > > > _______________________________________________ > Facebooker-talk mailing list > Facebooker-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/facebooker-talk >
Aurélien Malisart
2008-Jun-19 18:54 UTC
[Facebooker-talk] facebook apps developement "process"
Hi. Thanks for these replies. Set the callback url to be http://localhost[:port]/ and the app will run off> your machine, avoiding the need to commit just to test. If youre using FBML > rather than iframe then localhost won''t work ... you''ll need to specify an > externally accessible IP I think. > > That setup would imply that yes you would probably want to register a > production and development (with the developer mode ticked) app on FB. > > HTH >So, yes I''m using FBL. Not possible to imply using localhost:port Here''s a shameless plug:> > Check out Tunnlr: http://tunnlr.com > > It makes the tunneling hack effortless. That''s how we develop all of our > applications. > > MikeSeems good by not free. I''m just a student... I have multiple apps setup Dev - Staging and Production...> > For development I use an SSH Tunnel... Although I used to poke a hole in my > firewall and do port forwarding to my dev box. That doesn''t work when you > are at a coffee shop though. >Okay... On Thu, Jun 19, 2008 at 8:16 PM, Joseph Sofaer <joseph.sofaer at gmail.com> wrote:> Aur?lien, > Your other option is dynamic dns. > So you can use a service like > http://www.dyndns.com/services/dns/dyndns/ to get a url which they > will route to you. > You probably also have to set your router up to do port forwarding. So > have port 3000 go to you computer''s ip. > Then you want a development app, a production app and likely a staging app. > Best,Yes it''s a solution. But not very convenient if you often change of location. I''ve thought about synchronizing my dev app with rsync to my remote server for tests... -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/facebooker-talk/attachments/20080619/c9026893/attachment.html>
David Clements
2008-Jun-19 19:11 UTC
[Facebooker-talk] facebook apps developement "process"
Didn''t I hear about some project where you could run a mock facebook server locally? I am trying to remember. Anyone know what I am talking about? Dave On Thu, Jun 19, 2008 at 12:54 PM, Aur?lien Malisart < aurelien.malisart at gmail.com> wrote:> Hi. Thanks for these replies. > > Set the callback url to be http://localhost[:port]/ and the app will run >> off your machine, avoiding the need to commit just to test. If youre using >> FBML rather than iframe then localhost won''t work ... you''ll need to specify >> an externally accessible IP I think. >> >> That setup would imply that yes you would probably want to register a >> production and development (with the developer mode ticked) app on FB. >> >> HTH >> > > So, yes I''m using FBL. Not possible to imply using localhost:port > > Here''s a shameless plug: >> >> Check out Tunnlr: http://tunnlr.com >> >> It makes the tunneling hack effortless. That''s how we develop all of our >> applications. >> >> Mike > > > Seems good by not free. I''m just a student... > > I have multiple apps setup Dev - Staging and Production... >> >> For development I use an SSH Tunnel... Although I used to poke a hole in >> my firewall and do port forwarding to my dev box. That doesn''t work when >> you are at a coffee shop though. >> > > Okay... > > On Thu, Jun 19, 2008 at 8:16 PM, Joseph Sofaer <joseph.sofaer at gmail.com> > wrote: > >> Aur?lien, >> Your other option is dynamic dns. >> So you can use a service like >> http://www.dyndns.com/services/dns/dyndns/ to get a url which they >> will route to you. >> You probably also have to set your router up to do port forwarding. So >> have port 3000 go to you computer''s ip. >> Then you want a development app, a production app and likely a staging >> app. >> Best, > > > Yes it''s a solution. But not very convenient if you often change of > location. > > > I''ve thought about synchronizing my dev app with rsync to my remote server > for tests... > > > _______________________________________________ > Facebooker-talk mailing list > Facebooker-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/facebooker-talk > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/facebooker-talk/attachments/20080619/73b2c90e/attachment.html>