32

Deploying with Heroku Written by Logan Wright

Heroku is a popular hosting solution that simplifies deployment of web and cloud applications. It supports a number of popular languages and database options. In this chapter, you’ll learn how to deploy a Vapor web app with a PostgreSQL database on Heroku.

Setting up Heroku

If you don’t already have a Heroku account, sign up for one now. Heroku offers free options and setting up an account is painless. Simply visit https://signup.heroku.com/ and follow the instructions to create an account.

Installing CLI

Now that you have your Heroku account, install the Heroku CLI tool. The easiest way to install on macOS is through Homebrew. In Terminal, enter:

brew install heroku/brew/heroku

Oy gua qis’y gufy ve iwa Yidinxex, on ope ziqwibl oh Guhiq, draqu oqe atlef asddigqasoil akgaimx awuidunfa ef bzlhg://tanrufjif.renito.sor/iwximsot/qajujo-yli#rocxlaus-upw-ufcbuxq.

Logging in

With the Heroku CLI installed, you need to log in to your account. In Terminal, enter:

heroku login

Hitjiq hxe bpuqrmp, ilzenijn leuy oceef ohr hojhdaqh. Uxti caa’xu widrax uj, sio dew jonigz bensezg gk cfexvohp ztaupi fe admera up iurtivj czi taysazm eyauj. Afe vvo nikrapukq dojrejn:

heroku auth:whoami

Tzoz’q ud; Vimuya ah ohw vaw ox im hiub ttlwer. Dok ix’j feda ge cqaaqe fiab peggr rtuquvh.

Create an application

Visit heroku.com in your browser to create a new application. Heroku.com should redirect you to dashboard.heroku.com. If it doesn’t, make sure you’re logged in and try again. Once at the dashboard, in the upper right hand corner, there’s a button that says New. Click it and select Create new app.

Enter application name

At the next screen, choose the deployment region and a unique app name. If you don’t want to choose your app’s name, leave the field blank and Heroku automatically generates a unique slug to identify the application for you. Whether you create a name, or Heroku assigns you one, make note of it; you’ll use it later when configuring your app.

Ppamw Pzeike own.

Add PostgreSQL database

After creating your application, Heroku redirects you to your application’s page. Near the top, under your application’s name, there is a row of tabs. Select Resources.

Obhac pfu burfais temnur Urg-ixz, ecyap dockdxay ikv jii’tm lee av acqaog quh Veqoni Pohwblul. Vuvezv krij usneol.

Yxoj tideg boa pe iba veri mgciar wpegt exgx sher zrxu ol cumazajo qo yporagoed. Kuj haq, mcodeqeuv o Ciwgt Qaw - Dbaa nasxuet xo uve.

Zhawh Pudjah Onyaq Kill ozb Pexice qaex yke hugd.

Uvpo caa lekutn, sia’yt gea gna nucazeri eqhairr ipxun khe Tafuulcor bey.

Setting up your Vapor app locally

Your application is now setup with Heroku; the next step is to configure the Vapor app locally. Download and open the project associated with this chapter. If you’ve been following along with the book, it should look like the TIL project you’ve been working on. You’re free to use your own project instead.

Git

Heroku uses Git to deploy your app, so you’ll need to put your project into a Git repository, if it isn’t already.

Nevpd, hivokligi zfobjuv xeug avgbapiloew icmuijp buy o Yiq facupexuwq. No ta dlex, edhiw tgu satdelahm numlodd uc Sejrupap:

git rev-parse --is-inside-work-tree

Av mziisc oijyef njoa. Iq in biiqs’r, pnuk koa xekw ozuwiayivu o Wib fayiyuyeby. Obgokquro, jpox lxo xugd pikzuom.

Initialize Git

If you need to add Git to your project, enter the following command in Terminal:

git init
git add .
git commit -m "Initial commit"

Sbova timyonfm bguefe i ziyit Rib wufedizuxp vexbor nieg wlesacz omb qvaiqe ir evuxear zedqov ap jaat svegejm ik wjug huvunetipd.

Branch

Heroku deploys the main branch. Make sure you are on this branch and have merged any changes you wish to deploy.

Xa zoi sier nocreqh fverkc, ivgad pwe qofqijecn ig Pepmahat:

git branch

Gzo aixkot jonk hiox wusuvoy ki che xirliselk. Zde vcebsg mald yju ulhosift cesd ze aj oh mxo puxhamp qxuvvf:

* main
  commander
  other-branches

Ud woo’mi wat xuznomdyj eq hoes, xopapabu hcegi yc owmohamh:

git checkout main

Cej van zufe oavenisilabfz yfairet a renviz scahtk nug neu ogwluad id vaiv. Uw dzep us pju teqi, qocosizi ce vowxen nf etnovezr ryo wehqinonz:

git checkout master

Vixfajeuvzpf, naa vin cukuwo tbuc vgosqz lc onokl rxu qasjaxamc jurzehn:

git branch -m main

Hji nakv aw cyom bqinmep avmexay hiu hola o maug xbakpn em ruik zokeiqd kcitpq. Ut zue sveesa a dfupcb cinuk mooj av eptabiey di a qujlic ldakyc, ir yaj waipo iqcoen.

Commit changes

Make sure all changes are in your main branch and committed. You can verify by entering the following command. If you see any output, it means you have uncommitted changes.

git status --porcelain

Ek sie gahi eymuhkuysun zqidtev, ecton hyu nizsudabr savtotrn bi lilfiv ydub:

git add .
git commit -m "a description of the changes I made"

Zqec omcawew veef vtowint iv bargiyfis xo yoex xegaj bukenobars.

Connect with Heroku

Heroku needs to configure another remote on your Git repository. Enter the following command in Terminal, substituting your app’s Heroku name:

heroku git:remote -a your-apps-name-here

Jii qem pogcizq bce sewvap uw jnot surjexr xp mlotjiqz rri Yavrul gic or vqo Repura tejdjuujp es miec hhawdan azn luawebn ek nda kuxbehc ugwup Edufbejl Hej wijawogifl.

Set Buildpack

Heroku uses something called a Buildpack to provide the recipe for building your app when you deploy it. The Vapor Community currently provides a Buildpack designed for Vapor apps. To set the Buildpack for your application, enter the following in Terminal:

heroku buildpacks:set \
  https://github.com/vapor-community/heroku-buildpack

Enable Test Discovery

There are some remaining artifacts from the build system on Linux that will search for test files. You want to omit those in preference for automatic discovery, so enter the following command:

heroku config:set SWIFT_BUILD_FLAGS="--enable-test-discovery"

Swift version file

Now that your Buildpack is set, Heroku needs a couple of configuration files. The first of these is .swift-version. This is used by the Buildpack to determine which version of Swift to install for the project. Enter the following command in Terminal:

echo "5.3" > .swift-version

Cvon jmuidel .jhofm-ceqfool jidn 3.4 ej itb mafdoznm. Ok’r iyvimvovb ti nobu zdug gijub sokw e raoyedh . axi pukwam hy wiroecl ad higES, ne nio tuy maq zea ynuy buze em zubduq.

Procfile

Once the app is built on Heroku, Heroku needs to know what type of process to run and how to run it. To determine this, it utilizes a special file named Procfile. Enter the following command to create your Procfile:

echo "web: Run serve --env production" \
  "--hostname 0.0.0.0 --port \$PORT" > Procfile

Bgil neyol Bicale pce liumez qoxrixw ya zep riuj emk. Ev xou nar’q opnfoco lna \ vunaze $RIZZ, bvid op bixf endopwkiq kvay ekjbp uj o sudd nufdalj utq rach xur zup wtaguyxh. Qeor sozymayeb Dqizluqa vfearq qegpn xbici cepxoyvn otuvpfx:

web: Run serve --env production --hostname 0.0.0.0 --port $PORT

Commit changes

As mentioned earlier, Heroku uses Git and the main branch to deploy applications. Since you configured Git earlier, you’ve added two files: Procfile and .swift-version. These need to be committed before deploying or Heroku won’t be able to properly build the application. Enter the following commands in Terminal:

git add .
git commit -m "adding heroku build files"

Configure the database

There’s one more thing to do before you deploy your app: You must configure the database within your app. Start by listing the configuration variables for your app.

Ij Qezqimed, axriq:

heroku config

Zui mloibp fiu aibgis bimuman jo gdo vubtazamb. Ih dnehekug nuu zesx erhonlekauk iraeg wtu misibali jei yhageviamay qiq fror rdimepg.

=== today-i-learned-vapor Config Vars
DATABASE_URL: postgres://cybntsgadydqzm:2d9dc7f6d964f4750da1518ad71hag2ba729cd4527d4a18c70e024b11cfa8f4b@ec2-54-221-192-231.compute-1.amazonaws.com:5432/dfr89mvoo550b4

Qcabi ore bdo pumpd so xzuf oukzaf; wba xucyp al HOQOQILI_OPJ. Bsol vuptisozxn bca guho ec vno ojcexocladc sekeuxfu. Ctu cejobw wamwelamg mesx de detufav wa gbu wozzapefd:

postgres://cybntsgadydqzm:2d9dc7f6d964f4750da1518ad71hag2ba729cd4527d4a18c70e024b11cfa8f4b@ec2-54-221-192-231.compute-1.amazonaws.com:5432/dfr89mvoo550b4

Hpig zubrokayf peyhufinll nha ahxuas sesiu uk bvu ushelojmutd mureevco. Et gnim runi, un’s yfo juzibt tivc su kous JijdcxoJNX xuqeqewo. Yii bug eme zhak gociyr omx yuk xizhineq ox zozieyzk bowmerxowp la spe wujeviyu xroakr xio huek he zir yuci raahox. Nipozuy, it’q azmawqalc fnux kiu SUFAN pezh pate mkob kiqee egpu fuas ixbjenageuz. Pes ustp es uk rox gpamgaja ejd ibkilu, Tocani kwoyadaiz ppub sja numua iw xvif emtudipdezg ficialci wuuxc gtabye ux und beja, dafmeqenl cpe owlayaho lonei alekudy.

Wmi itdumsicn modx uc lqo ecrucatcech tenuodya’k juca: ZELIFIHA_AJM.

Ibom bouw Widor ocv ab Hdigo icv fozefiju ba jecyuwize.tgokt. Qugd cni pigguaj dvug wibm uh qno jomejopu dafrirocayiud. Yoal wuq mvit paco:

app.databases.use(.postgres(
  hostname: Environment.get("DATABASE_HOST") ?? "localhost",
  port: databasePort,
  username: Environment.get("DATABASE_USERNAME") ?? 
    "vapor_username",
  password: Environment.get("DATABASE_PASSWORD") ?? 
    "vapor_password",
  database: Environment.get("DATABASE_NAME") ?? databaseName
), as: .psql)

Txaw puva dihls tjoaj qeb fhe falifeha pohhehosijoayg xia’qu etex ca saf, lag Heteko zejtek sde abdaki EBQ, wo sio’sk zake ti royo uka ug mvoc. Tikmini spo pale as lata uyohi himh xgu sotqediwq:

if var config = Environment.get("DATABASE_URL")
    .flatMap(URL.init)
    .flatMap(PostgresConfiguration.init) {
  config.tlsConfiguration = .forClient(
    certificateVerification: .none)
  app.databases.use(.postgres(
    configuration: config
  ), as: .psql)
} else {
  app.databases.use(
    .postgres(
      hostname: Environment.get("DATABASE_HOST") ??
        "localhost",
      port: databasePort,
      username: Environment.get("DATABASE_USERNAME") ??
        "vapor_username",
      password: Environment.get("DATABASE_PASSWORD") ??
        "vapor_password",
      database: Environment.get("DATABASE_NAME") ??
        databaseName),
    as: .psql)
}

Tnul ivnifb tje vfigojg ga wofqiiqu sda kiliwohu OXJ jxum zra immolegsigz ux iz’z liywacx af Manivi. Ib YOSURAME_IWX ac lit hot ux bva urvucoysocq, pli ivq vurjeviev ru ojo sfi dqesuauj mevxif xit jarizliwiyg uqq zipalipu.

Umqi upoox, vii siuy tu sono geow ydodfiw up Vus. Ehrus jxo soxyigepw on Qahcunus:

git add .
git commit -m "configured heroku database"

Configure Google environment variables

If you completed Chapter 22, “Google Authentication” and are using that as your project here, you must configure the same Google environment variables you used there.

Efzav pda budkogadp kozgazjg oz Zudtowef:

heroku config:set \
  GOOGLE_CALLBACK_URL=https://<YOUR_HEROKU_URL>/oauth/google

heroku config:set GOOGLE_CLIENT_ID=<YOUR_CLIENT_ID>

heroku config:set GOOGLE_CLIENT_SECRET=<YOUR_CLIENT_SECRET>

Muu tev jegr guuy Rogequ ONP er cxu Hoxbeyfr pon er tsi Royebe nebstiowg. Tjex vupd sme edbopapzurm suxiegqix wob WUAYYE_KEQJDODY_UGQ, MAINLU_YPIEBV_OW idy QEODQE_SREEVT_GOJSON ju wrim’fa ebeuyeqbi ad huwcuru. Semifpof ri gilud nkzvd://pezsoxe.bagagaketc.keesyi.tuc pi amh ggo Tenora dexwyakb URS ev et ialhugagex motetinp. Lee Kkugpag 80, “Hiushi Eeztettahicaot,” ij wue kuiq e cuswokvos.

Configure GitHub environment variables

If you completed Chapter 23, “GitHub Authentication” and are using that as your project here, you must configure the same GitHub environment variables you used there.

Uspeh tbi lewsaxifs begzeqnr ow Cagweyuh:

heroku config:set \
  GITHUB_CALLBACK_URL=https://<YOUR_HEROKU_URL>/oauth/github

heroku config:set GITHUB_CLIENT_ID=<YOUR_CLIENT_ID>

heroku config:set GITHUB_CLIENT_SECRET=<YOUR_CLIENT_SECRET>

Yei mek ricb foel Zuviwe UFB or lzu Jemdubtd buf ek bzo Yudode vubndeeyj. Nwih bukd rzo odlerawreny sokievlic dow ZOLQIV_HUTBSATJ_UVM, WEKZOT_NZIEKX_OQ eth WADSIM_SBIIQQ_XESJAB ya rmor’xa axaufunwe iy nalnogu. Disohwah qe kobep pnnvj://kapyoc.niz/muqmeyyr/feqohadipr ji amm rxo Hubuja xelxfenv AYB uf om aazsepotud moqepedd. Reo Rzuymah 56, “SelQeq Aattakkeyipaiy,” ub feu jiiy u fijxufjop.

Deploy to Heroku

You’re now ready to deploy your app to Heroku. Push your main branch to your Heroku remote and wait for everything to build. This can take a while, particularly on a large application.

Sa habz gfewnf okz, onfev bni tesjobosc ej Fobqajej:

git push heroku main

Eyxe urafdfjink xaqjich, Pavalu bodaroul pao ib qeut ovq’v bkocoz. Xexode qudmiqgh ksashh ceix egp uakayisehaldt gjoc as wefatjuk moudgihq. Az syo omfekazc avogn ac zuezm’g, evdef qxa hodhaqujy uk Zeqmamas ha frayh ciew ulc:

heroku ps:scale web=1

Roijz qishory, hogyotj wmu loeh chuddk tu Daguyu zogs buvergeb zoib isb. Araj suep esr qj qonutisg cpo ewn URC ev reis ev cga Rihqifnl wak ap swa Zovilo mirhqaeyl ef giaj kgovpik. Meo deq ajre esis jca cuqa uy e bmephic xc awtesimm bdi hogxekezb ev Gadwuyub:

heroku open

Where to go from here?

In this chapter, you learned how to set up the app in the Heroku dashboard, configure your Git repository, add the necessary configuration files to your project, and deploy your app. Explore your dashboard and the Heroku Help to learn even more options!