You can use a callback URL like the following to develop locally.

http://dev.local:3000/authenticated

Then put your dev, stage, prod callback URLs in a config.  Your app
should work the same regardless of the server/environment it is
running on.

I also have different twitter accounts for dev/stage and prod.  My
prod twitter account is http://twitter.com/imby while dev & stage are
http://twitter.com/imbyTest  That way the @imby lists and feed does
not contain test tweets and whatnot.  Again, this is contained in a
config file so that prod => @imby and everything else => @imbyTest


On Fri, Apr 23, 2010 at 12:19 PM, Patrick Kennedy <kenned...@gmail.com> wrote:
> Yes, Twitter requires a callback URL. Make a test page to display (or
> save to file) your oAuth tokens.  Embed those tokens into your local
> test page (and remove that helpful test page on hosted server).
> Develop locally, and add if-then blocks, depending if you are local or
> remote.  That way, you can develop locally, and upload same file, as
> it will work for the remote as well.  When remote, instead of "saved"
> tokens, use the "live" tokens from the handshake process.
>
> ~PK
>
> On Fri, Apr 23, 2010 at 7:13 AM, kaps <kap...@yahoo.com> wrote:
>> Hi,
>>
>> How do you folks test your Twitter apps before uploading them to your
>> hosting servers?
>> Doesn't the Twitter callback URL have to be a valid website?  How can
>> we test locally?
>>
>>
>> Thanks,
>> kaps
>>
>>
>> --
>> Subscription settings: 
>> http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
>>
>



-- 
imby - in my back yard
An Experiment in Local Professional Networking
http://madison.imby.info/p/Philip.Crawford

Reply via email to