<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ulhas Mandrawadkar on Medium]]></title>
        <description><![CDATA[Stories by Ulhas Mandrawadkar on Medium]]></description>
        <link>https://medium.com/@ulhas_sm?source=rss-fdd8a334609a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0ykWWlXA3WTmBauVEl0ntA.jpeg</url>
            <title>Stories by Ulhas Mandrawadkar on Medium</title>
            <link>https://medium.com/@ulhas_sm?source=rss-fdd8a334609a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:27:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ulhas_sm/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Dockerize your SailsJS app]]></title>
            <link>https://medium.com/the-procedure/dockerize-your-sailsjs-app-6e418c8f7cab?source=rss-fdd8a334609a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e418c8f7cab</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[django]]></category>
            <category><![CDATA[sailsjs]]></category>
            <dc:creator><![CDATA[Ulhas Mandrawadkar]]></dc:creator>
            <pubDate>Tue, 11 Apr 2017 17:22:18 GMT</pubDate>
            <atom:updated>2017-04-11T17:22:18.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*vDD4qLH0yWXTO7b7TJguLA.jpeg" /><figcaption>What do we want? Reliable deployments!</figcaption></figure><p>We, at The Procedure, are huge fans of <a href="https://github.com/pydanny">pydanny’s</a> work. His cookiecutter scripts for creating Django apps and packages are staple in our development toolkit. Recently, for one of our Django apps, we used <a href="https://www.docker.com/">Docker</a> for deployment. <a href="https://github.com/pydanny/cookiecutter-django">Cookiecutter-django</a> gave us a fairly straightforward, production-ready docker-compose file. We decided to use a similar setup in one of our SailsJS app as well. Let us show you how.</p><h4><strong>Prerequisite</strong></h4><p>Make sure you have already <a href="https://docs.docker.com/compose/install/">installed both Docker Engine and Docker Compose</a> on your machine. You don’t need to install Node or Postgres, as both are provided by Docker images.</p><h4><strong>1. Define services in a Compose file</strong></h4><p>Create a docker-compose.yml file in your project directory and paste the following.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/262eb89f9f16d0bdfd992cebd1e823d0/href">https://medium.com/media/262eb89f9f16d0bdfd992cebd1e823d0/href</a></iframe><p>This Compose file defines two services, postgres and sails.</p><p>The sails service:</p><ul><li>Uses an image that’s built from the Dockerfile in the sails compose directory</li><li>Defines the context as the current directory</li><li>Specifies a command to be executed once the container is built</li><li>Mounts the project directory on the host to /app inside the container, allowing you to modify the code without having to rebuild the image</li><li>Specifies environment variables</li><li>Forwards the exposed port 8000 on the container to port 8000 on the host machine</li><li>Specifies postgres service as dependency and also mentions it as a link to sails service</li></ul><p>The postgres service:</p><ul><li>Uses an image that’s build from the Dockerfile in the postgres compose directory</li><li>Specifies volumes to be created/used for data and backup</li><li>Specifies environment variables</li></ul><h4><strong>2. Create the SailsJS Dockerfile</strong></h4><p>In this step, you write a Dockerfile that builds a Docker image. The image contains all the dependencies the SailsJS application requires, including node.</p><p>In compose/sails/ directory, create a Dockerfile and paste the following</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b1ebb137d753394819a52c17313137ca/href">https://medium.com/media/b1ebb137d753394819a52c17313137ca/href</a></iframe><p>This tells Docker to:</p><ul><li>Build an image starting with the latest Node image.</li><li>Install sails and grunt globally in the container</li><li>Copy package.json from the project directory to the container and run npm install</li><li>Copy scripts from the compose directory to container and change it’s permission to be an executable</li><li>Set the working directory to /app.</li><li>Set the entrypoint of the container to be entrypoint.sh</li></ul><h4><strong>3. Spin up </strong><strong>postgres instance before lifting SailsJS</strong></h4><p>In compose/sails/ directory, create a entrypoint.sh and paste the following</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4157e225662b98ae8cacb68d1593c7e9/href">https://medium.com/media/4157e225662b98ae8cacb68d1593c7e9/href</a></iframe><p>This script tries starts the postgres instance. It waits until the instance is started to execute the command mentioned in start-dev.sh — sails lift -- port 8000 --verbose</p><h4><strong>4. Profit!!!</strong></h4><p>There are few more files that you will need to setup. The files can be found <a href="https://github.com/the-procedure/docker-sails">here</a>.</p><p>When you’re done with the setup all you have to do is run these two commands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ENtdr2GvKxwwQGTqNaPrg.gif" /><figcaption>Profit!</figcaption></figure><ul><li>docker-compose build will build the images, create volumes and install dependencies</li><li>docker-compose up will start the services and lift your SailsJS app</li></ul><p>The complete repository with these files is here — <a href="https://github.com/the-procedure/docker-sails">https://github.com/the-procedure/docker-sails</a></p><p><em>At Procedure, we write our code with love, look at it with pride and always await more adventures! Want to work with exciting new tech and a fantastic team? Apply </em><a href="https://goo.gl/rq65Kr"><strong><em>here</em></strong></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e418c8f7cab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-procedure/dockerize-your-sailsjs-app-6e418c8f7cab">Dockerize your SailsJS app</a> was originally published in <a href="https://medium.com/the-procedure">Procedure</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Fastlane to distribute private frameworks]]></title>
            <link>https://medium.com/rubber-duck/using-fastlane-to-distribute-private-frameworks-df357af1dc21?source=rss-fdd8a334609a------2</link>
            <guid isPermaLink="false">https://medium.com/p/df357af1dc21</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[fastlane]]></category>
            <dc:creator><![CDATA[Ulhas Mandrawadkar]]></dc:creator>
            <pubDate>Sat, 10 Sep 2016 03:33:58 GMT</pubDate>
            <atom:updated>2016-09-10T03:43:30.408Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*UchIRfbd6orknkV4FZAwTw.png" /></figure><p>At <a href="http://www.hypertrack.io/">HyperTrack</a>, we are building APIs and SDKs which enable developers to track and trace local deliveries. Developers integrate HyperTrack’s tracking SDK into the app that drivers use to mark the start and end of their pickup and delivery tasks. We deploy our SDKs as frameworks and distribute it via <a href="http://www.cocoapods.org/">Cocoapod</a>s — a popular dependency management tool. Having lost few hours every time we deployed our SDK, we gave Fastlane a spin and found ourselves pleasantly surprised with the result.</p><h4>Breaking down the deployment</h4><p>Deploying a framework to a private CocoaPods repo is an involved process, with many moving parts, which can prove to be erroneous and time consuming. Moreover, if we wanted to test our changes, we would have to repeat these steps, and that meant longer iteration cycles. Take a look at the steps involved in releasing our SDKs manually.</p><h4>Manual Deployment Steps</h4><ol><li>Bump version no. for HTCommon</li><li>Bump version no. for HTSDKVersion constant in HyperTrack.h</li><li>Build universal frameworks, for each of using build scrip</li><li>Zip frameworks</li><li>Upload the framework to s3</li><li>Update podspec and push it to private pod repo</li><li>Build the example app</li><li>Upload example app to Crashlytics</li><li>Create documentation and upload them</li></ol><p>Although we used a <a href="https://gist.github.com/ulhas/3d995e416fd3286dfc06">script</a> to build universal frameworks (#3), we felt the need to automate the entire deployment process. Writing rakefiles or shell scripts seemed to be a good option but that meant dedicating engineering resources and felt like reinventing the wheel. We wanted to lower our barrier for shipping so we could focus on building.</p><h4>Enter Fastlane</h4><p><a href="http://www.fastlane.tools/">Fastlane</a> is the cool new kid on the block who everyone wants to be friends with. Its an <a href="https://github.com/fastlane/fastlane">open source</a> collection of tools for automating iOS (and some of Android) deployment process.</p><p><strong>Diving in</strong></p><p>Let’s see few examples of how the manual deployment steps corresponds to private lanes in our Fastfile.</p><p><strong>Bump version no. for</strong> HTCommon, HTTransmitter <strong>&amp;</strong> HTConsumer</p><p>Here we’ve defined a private lane named <em>increment_framework_version</em> which takes in framework and version as inputs and increments the version no. in the plist file.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/207a6c0b9cf66c0f9cea59fc3ce8b778/href">https://medium.com/media/207a6c0b9cf66c0f9cea59fc3ce8b778/href</a></iframe><p><strong>Zip frameworks</strong></p><p>In the package_framework lane we use FileUtils methods to delete previous frameworks, copy the built framework to new directory and zip it. This allows us to later push the zipped framework on S3.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/619e57759f442a26e1d1e2f98204f43f/href">https://medium.com/media/619e57759f442a26e1d1e2f98204f43f/href</a></iframe><p><strong>Upload framework to S3</strong></p><p>Fastlane comes with an out-of-box solution for uploading .ipa files to S3 but none for uploading a zip file. So we wrote a custom <a href="https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md">action</a> which uploaded the zipped framework to S3 using ruby gem aws.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cd90e7262c8f795aed67fd7af49f177a/href">https://medium.com/media/cd90e7262c8f795aed67fd7af49f177a/href</a></iframe><p>You can find rest of the lanes in our Fastfile. Link below.</p><p><strong>Putting it all together</strong></p><p>So how does it all orchestrate together? Take a look at our <a href="https://gist.github.com/ulhas/e8e529d08849b8cda947">Fastfile</a>.</p><p>To release our SDK in production we simply run fastlane release_production bump_type:major or fastlane release_production version:”0.2.1&quot; and all the manual steps mentioned previously is taken care automagically within seconds. The frameworks get deployed, an example is released on Crashlytics and notifications are sent to our slack channels.</p><p>You can find our Fastfile, custom actions and helpers <a href="https://gist.github.com/ulhas/">here</a>.</p><h4>Contributing to Fastlane</h4><p>When deploying a podspec, with internal dependencies, to a private repo, a source needs to be specified for linting. Fastlane didn’t have a solution to mention a private repo as source while pushing pod. For our needs, the HTTransmitter and HTConsumer SDKs have dependency HTCommon — a repo with common code used by both libraries. So, we wrote a custom action which took sources as one of the inputs which fixed the broken pod_push action. Later, we contributed back to Fastlane by adding support for sources in the pod_push action. Here is the merged <a href="https://github.com/fastlane/fastlane/pull/1113">pull request</a>.</p><p>Fastlane has saved us lot of engineering time that keeps us focused on building cool stuff for you. We are passing along the favor. With HyperTrack, save yourself a lot of engineering time to build tracking so you can focus on building cool stuff for your customers.</p><p>Originally posted at <a href="https://blog.hypertrack.io/2016/03/21/using-fastlane-to-distribute-private-frameworks/">HyperTrack</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df357af1dc21" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rubber-duck/using-fastlane-to-distribute-private-frameworks-df357af1dc21">Using Fastlane to distribute private frameworks</a> was originally published in <a href="https://medium.com/rubber-duck">Rubber Duck</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HyperTrack’s tracking experience]]></title>
            <link>https://medium.com/hypertrack/hypertracks-tracking-experience-556278645dda?source=rss-fdd8a334609a------2</link>
            <guid isPermaLink="false">https://medium.com/p/556278645dda</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Ulhas Mandrawadkar]]></dc:creator>
            <pubDate>Tue, 19 Apr 2016 07:38:09 GMT</pubDate>
            <atom:updated>2016-10-17T07:40:53.577Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>HyperTrack’s tracking experience</strong></p><p>HyperTrack’s tracking experience for the end-user is a core part of our tracking-as-a-service offering. SDKs are available for iOS, Android and Web so you can integrate it with your product experience. In this post, I dive deeper into the tracking experience and settings.</p><h4>The experience</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F163350593&amp;url=https%3A%2F%2Fvimeo.com%2F163350593&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F566655332_295x166.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="540" height="958" frameborder="0" scrolling="no"><a href="https://medium.com/media/459e3d55e432b86f6fa6298f8caa8e55/href">https://medium.com/media/459e3d55e432b86f6fa6298f8caa8e55/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F163350592&amp;url=https%3A%2F%2Fvimeo.com%2F163350592&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F566655336_295x166.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="358" height="640" frameborder="0" scrolling="no"><a href="https://medium.com/media/60e265e352019c2033054ea61aab9fa0/href">https://medium.com/media/60e265e352019c2033054ea61aab9fa0/href</a></iframe><p><strong>Live tracking</strong></p><p>In the videos, you can see the in-app tracking view for iOS and Android (the tracking view for Web is available in the <em>How it works</em> section of our <a href="http://hypertrack.io/">homepage</a>). The tracking view shows the driver moving in realtime on the map. The driver marker denotes the type of vehicle — bike, car, van or walk. The marker on the destination location displays ETA for the current trip. The top bar shows the trip meter and status with destination address/location. The overlay bar at the bottom shows the driver identity and contact.</p><p>Behind the scenes, the Driver SDK integrated into the driver app sends a location stream to our servers. The location stream is then cleaned and filtered resulting in a smooth animation. Based on location, speed and extrinsic factors, an accurate ETA is computed. All of this is rendered cleanly into a tracking view. In-app and web SDKs let you integrate this tracking view into your end-user experience with settings to switch the key elements on or off.</p><p><strong>Trip Status</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*kaz1wilPQHcVDkjR." /><figcaption>Trip Status</figcaption></figure><p>At the top of the tracking view, trip status shows <em>ON THE WAY</em> when the driver has left the start location and is in motion. The status changes to <em>ARRIVING</em> when the driver is a couple of minutes away from the destination. It transitions to <em>ARRIVED</em> when we detect that the motion has stopped, suggesting that the vehicle is parked and the driver is checking in to complete the task. Once the order is marked delivered, the status displays <em>DELIVERED</em>. In case of delays, there are granular statuses conveying the reason for delay. For a complete list of statuses, <a href="https://www.hypertrack.io/#request_access">request access</a> to our documentation.</p><p><strong>Trip meter</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/0*2dopg1jxh_prIVpw." /><figcaption>Trip meter</figcaption></figure><p>Trip meter shows duration and distance along with the date for that trip. Under the meter, you can see the start address with the actual time of departure and destination address with the current ETA. The trip meter transitions to a trip summary once the trip has ended. If we fail to resolve the start and end locations to an address, we fall back to latitude and longitude of the locations.</p><p><strong>Driver identity and contact</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/0*9dksMxuPoUYSyC_X." /><figcaption>Driver identity and contact</figcaption></figure><p>The overlay bar at the bottom shows the driver identity and contact, and a short cut for order lookup. To the left is the driver’s photo followed by name to put the end-user at ease about who to expect. To the right is the call button followed by a shortcut to look up the order so the end-user can prepare to receive the order. The call button and order lookup buttons give callbacks to the host application. You can choose to handle these callbacks as appropriate for your application.</p><p><strong>Order lookup</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/0*l7LW4v1W4lPevCI2." /><figcaption>Order lookup</figcaption></figure><p>The order lookup button shows an overlay with details for the current order. This visual experience and content can be designed by you in a way that is consistent with your app experience. This feature comes in handy to get the end-user ready to receive the order, thus making it efficient for the driver and them.</p><p><strong>Trip summary</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/1*uNDLKHOW2HlDzV0zZ8lPBA.png" /><figcaption>Trip summary</figcaption></figure><p>Once the trip has ended, the map transitions to a summary view. Live tracking is stopped, driver and destination markers disappear, and trip meter is expanded to a detailed version. Map plots a polyline with the actual path that the driver took for the trip. The color code of source and destination locations is consistent with the trip meter.</p><h4>Settings</h4><p>The out-of-the-box tracking view is available to integrate within your product experience. Settings to switch key UI elements on or off have been provided through the APIs. Here is a list of settings available:</p><ul><li>Toggle visibility of driver identity and contact</li><li>Toggle visibility of trip meter</li><li>Toggle visibility of order lookup button</li><li>Custom markers for driver and destination</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*HS5ges93vCuAe-P_5WiC_Q.gif" /><figcaption>Customizations</figcaption></figure><h4>Integration</h4><p>HyperTrack’s tracking experience is packaged as an SDK that you can just drop into your app with a few lines of code. Since all the information is rendered into one tracking view, you can integrate it within the order flow of your app. Further, the tracking view does not need to consume the entire screen. It is a pluggable component which you can easily embed into the real estate you provide within your app.</p><p>We’ve worked hard to make it easy for developers to integrate HyperTrack’s tracking experience into your product experience. We would love for you to <a href="https://dashboard.hypertrack.io/signup">try it out</a> and give us your feedback.</p><p><em>Originally published at </em><a href="https://blog.hypertrack.io/2016/04/19/hypertracks-tracking-experience/"><em>blog.hypertrack.io</em></a><em> on April 19, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=556278645dda" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypertrack/hypertracks-tracking-experience-556278645dda">HyperTrack’s tracking experience</a> was originally published in <a href="https://medium.com/hypertrack">HyperTrack</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Fastlane to distribute private frameworks]]></title>
            <link>https://medium.com/hypertrack/using-fastlane-to-distribute-private-frameworks-8587578cf41c?source=rss-fdd8a334609a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8587578cf41c</guid>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Ulhas Mandrawadkar]]></dc:creator>
            <pubDate>Mon, 21 Mar 2016 09:54:04 GMT</pubDate>
            <atom:updated>2016-10-12T05:50:20.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*UchIRfbd6orknkV4FZAwTw.png" /></figure><p>At <a href="http://www.hypertrack.io/">HyperTrack</a>, we are building APIs and SDKs which enable developers to track and trace local deliveries. Developers integrate HyperTrack’s tracking SDK into the app that drivers use to mark the start and end of their pickup and delivery tasks. We deploy our SDKs as frameworks and distribute it via <a href="http://www.cocoapods.org/">Cocoapod</a>s — a popular dependency management tool. Having lost few hours every time we deployed our SDK, we gave Fastlane a spin and found ourselves pleasantly surprised with the result.</p><h4>Breaking down the deployment</h4><p>Deploying a framework to a private CocoaPods repo is an involved process, with many moving parts, which can prove to be erroneous and time consuming. Moreover, if we wanted to test our changes, we would have to repeat these steps, and that meant longer iteration cycles. Take a look at the steps involved in releasing our SDKs manually.</p><h4>Manual Deployment Steps</h4><ol><li>Bump version no. for HTCommon</li><li>Bump version no. for HTSDKVersion constant in HyperTrack.h</li><li>Build universal frameworks, for each of using build scrip</li><li>Zip frameworks</li><li>Upload the framework to s3</li><li>Update podspec and push it to private pod repo</li><li>Build the example app</li><li>Upload example app to Crashlytics</li><li>Create documentation and upload them</li></ol><p>Although we used a <a href="https://gist.github.com/ulhas/3d995e416fd3286dfc06">script</a> to build universal frameworks (#3), we felt the need to automate the entire deployment process. Writing rakefiles or shell scripts seemed to be a good option but that meant dedicating engineering resources and felt like reinventing the wheel. We wanted to lower our barrier for shipping so we could focus on building.</p><h4>Enter Fastlane</h4><p><a href="http://www.fastlane.tools/">Fastlane</a> is the cool new kid on the block who everyone wants to be friends with. Its an <a href="https://github.com/fastlane/fastlane">open source</a> collection of tools for automating iOS (and some of Android) deployment process.</p><p><strong>Diving in</strong></p><p>Let’s see few examples of how the manual deployment steps corresponds to private lanes in our Fastfile.</p><p><strong>Bump version no. for</strong> HTCommon, HTTransmitter <strong>&amp;</strong> HTConsumer</p><p>Here we’ve defined a private lane named <em>increment_framework_version</em> which takes in framework and version as inputs and increments the version no. in the plist file.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/207a6c0b9cf66c0f9cea59fc3ce8b778/href">https://medium.com/media/207a6c0b9cf66c0f9cea59fc3ce8b778/href</a></iframe><p><strong>Zip frameworks</strong></p><p>In the package_framework lane we use FileUtils methods to delete previous frameworks, copy the built framework to new directory and zip it. This allows us to later push the zipped framework on S3.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/619e57759f442a26e1d1e2f98204f43f/href">https://medium.com/media/619e57759f442a26e1d1e2f98204f43f/href</a></iframe><p><strong>Upload framework to S3</strong></p><p>Fastlane comes with an out-of-box solution for uploading .ipa files to S3 but none for uploading a zip file. So we wrote a custom <a href="https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md">action</a> which uploaded the zipped framework to S3 using ruby gem aws.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cd90e7262c8f795aed67fd7af49f177a/href">https://medium.com/media/cd90e7262c8f795aed67fd7af49f177a/href</a></iframe><p>You can find rest of the lanes in our Fastfile. Link below.</p><p><strong>Putting it all together</strong></p><p>So how does it all orchestrate together? Take a look at our <a href="https://gist.github.com/ulhas/e8e529d08849b8cda947">Fastfile</a>.</p><p>To release our SDK in production we simply run fastlane release_production bump_type:major or fastlane release_production version:”0.2.1&quot; and all the manual steps mentioned previously is taken care automagically within seconds. The frameworks get deployed, an example is released on Crashlytics and notifications are sent to our slack channels.</p><p>You can find our Fastfile, custom actions and helpers <a href="https://gist.github.com/ulhas/">here</a>.</p><h4>Contributing to Fastlane</h4><p>When deploying a podspec, with internal dependencies, to a private repo, a source needs to be specified for linting. Fastlane didn’t have a solution to mention a private repo as source while pushing pod. For our needs, the HTTransmitter and HTConsumer SDKs have dependency HTCommon — a repo with common code used by both libraries. So, we wrote a custom action which took sources as one of the inputs which fixed the broken pod_push action. Later, we contributed back to Fastlane by adding support for sources in the pod_push action. Here is the merged <a href="https://github.com/fastlane/fastlane/pull/1113">pull request</a>.</p><p>Fastlane has saved us lot of engineering time that keeps us focused on building cool stuff for you. We are passing along the favor. With HyperTrack, save yourself a lot of engineering time to build tracking so you can focus on building cool stuff for your customers.</p><p>Fastlane has saved us lot of engineering time that keeps us focused on building cool stuff for you. We are passing along the favor. With HyperTrack, save yourself a lot of engineering time to build tracking so you can focus on building cool stuff for your customers.</p><p><em>Originally published at </em><a href="https://blog.hypertrack.io/2016/03/21/using-fastlane-to-distribute-private-frameworks/"><em>blog.hypertrack.io</em></a><em> on March 21, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8587578cf41c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypertrack/using-fastlane-to-distribute-private-frameworks-8587578cf41c">Using Fastlane to distribute private frameworks</a> was originally published in <a href="https://medium.com/hypertrack">HyperTrack</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>