If you use one OAuth application for all three be warned that currently if a single user account is being used on all three it will only work on the environment that you last authorized it on. So if you are using your personal account on production and authorized it on development. Production will have old access tokens that will not work until you reauthorize on production. This is a known issue that Twitter is working on.
On Fri, Apr 10, 2009 at 02:43, Chad Etzel <jazzyc...@gmail.com> wrote: > > In your authorize reuqest URL you can manually set an "oauth_callback" > parameter which will override the URL set in your application setup > page. > > So, you can use one app for all of your different > test/dev/staging/live (sub)domains. > > -Chad > > On Fri, Apr 10, 2009 at 1:57 AM, Doug <dougire...@gmail.com> wrote: > > > > If I have dev/staging/prod environments defined as follows, do I need > > to create three separate oAuth apps on Twitter with the corresponding > > "Application Website" and "Callback URLs" defined in each one? > > > > 1. http://dev.example.com (pointing to my laptop external IP address) > > 2. http://staging.example.com (on my webhost server) > > 3. example.com (on my webhost server) > > > > Thanks, > > > > Doug > > > -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
