If you create a new deploy() method, I'll refactor the testflight stuff to
fit into that.  I just dont want to create new methods that we will only
take away again soon


On 27 February 2013 18:45, Valerio Santinelli <notifications@github.com>wrote:

> In lib/xcode/builder/base_builder.rb:
>
> > @@ -95,6 +95,23 @@ def testflight(api_token, team_token)
> >          testflight.upload(ipa_path, dsym_zip_path)
> >        end
> >
> > +      #
> > +      # Upload to web server
> > +      #
> > +      # The web object is yielded so further configuration can be performed before uploading
> > +      #
> > +      # @param protocol the protocol to use to upload files (ftp or ssh)
> > +      #
> > +      def web(protocol)
>
> Ok, that's fine by me. I just followed the testflight example and put the
> method in there, but the way you suggest is cleaner.
>
> It might take a while for me to figure out how to do this correctly as I'm
> new to Ruby development and I'm still learning the language.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/rayh/xcoder/pull/56/files#r3167139>
> .
>



-- 
Ray Hilton
(maker of mobile apps)
-
a: 13/243 Collins Street, Melbourne VIC 3000
m: 0430 484 708
w: http://rayh.com.au