<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Heroku on Justin B Kay's Blog</title><link>https://blog.jbkconsultingllc.com/tags/heroku/</link><description>Recent content in Heroku on Justin B Kay's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Sep 2021 08:16:17 -0600</lastBuildDate><atom:link href="https://blog.jbkconsultingllc.com/tags/heroku/index.xml" rel="self" type="application/rss+xml"/><item><title>Heroku Git Transport Feature Retirement</title><link>https://blog.jbkconsultingllc.com/posts/heroku-git-transport-feature-retirement/</link><pubDate>Wed, 29 Sep 2021 08:16:17 -0600</pubDate><guid>https://blog.jbkconsultingllc.com/posts/heroku-git-transport-feature-retirement/</guid><description>&lt;p&gt;We recently received an email from Heroku telling us that we would need to transition our deployments away from the ssh transport that we&amp;rsquo;ve been using on &lt;a href="https://semaphoreci.com/"&gt;Semaphore CI&lt;/a&gt; to deploy our Elixir Phoenix app. The &lt;a href="https://docs.semaphoreci.com/examples/heroku-deployment/"&gt;Semaphore deployment documentation&lt;/a&gt; only covers the ssh transport route. We needed to figure out how to move to the https deployments from our CI server. The &lt;a href="https://help.heroku.com/6JAIBWLM/how-do-i-deploy-my-app-with-heroku-s-http-git-transport-instead-of-ssh-git-transport"&gt;instructions&lt;/a&gt; in the email were&amp;rsquo;t too helpful as those steps had already been taken in our project, the Semaphore solution replaces https with ssh for deployments. The real issue was how to authenticate to Heroku now that SSH was off the table.&lt;/p&gt;</description></item></channel></rss>