Deploy a track
Make your track ready to go.
This guide explains how to deploy a track from Web UI and Instruqt CLI.
Deployment is making your track ready to go for sharing. Deployment differs for Web UI and Instruqt CLI:
🌐 Web UI
💻 Instruqt CLI
Deployment from Web UI involves re-building a track.
Deployment from Instruqt CLI involves pushing a track. Which automatically triggers a track re-build.

Deploy

Pick the Web UI or the Instruqt CLI route depending on your preference:
🌐 Web UI
💻 Instruqt CLI
For Web UI you need to re-build a track after every change you make to the track environment or the lifecycle scripts.

What changes make for a re-build?

  • Track environment changes These are changes you make in the Track details > Sandbox tab. And concern either adding or updating one or more of the following sandbox components:
    • Containers
    • Virtual machines
    • Google Cloud projects
    • AWS account
    • Azure subscriptions
  • Lifecycle scripts changes These are changes you make at Track details > Sandbox > Lifecycle scripts to the following scripts:
    • setup
    • cleanup

Before you begin

Make sure you have opened the Track overview page of the track you need to deploy.

Deploy

Deployment from Web UI involves re-building your track. Take the following steps to re-build:
  1. 1.
    Open your browser and go to play.instruqt.com. ↳ Instruqt shows your content.
  2. 2.
    Click the track you want to re-build. ↳ Instruqt shows the corresponding Track overview page.
  3. 3.
    Click Build track ⚙️. ↳ The Build track ⚙️ button turns gray while showing a spinner. And after a few seconds, you will see a little pop-up showing ✔Track built!
Deployment from Instruqt CLI involves pushing your local track to the Instruqt platform. Take the following steps to push the track:
  1. 1.
    Move into your track directory:
    1
    cd DIRECTORY_NAME
    Copied!
    ⇨ Replace DIRECTORY_NAME with your track directory.
  2. 2.
    Enter the following command:
    1
    instruqt track push
    Copied!
    ↳ Instruqt shows this output:
    1
    ==> Loading track files...
    2
    OK
    3
    ==> Checking challenges
    4
    OK
    5
    ==> Checking tabs
    6
    OK
    7
    ==> Checking scripts
    8
    OK
    9
    ==> Checking for leftover *.remote files
    10
    OK
    11
    ==> Reading track definition
    12
    OK
    13
    ==> Checking deltas
    14
    OK
    15
    ==> Pushing track
    16
    OK
    17
    ==> Pushing assets
    18
    Everything up-to-date
    19
    OK
    20
    ==> Updating local track:
    21
    OK
    22
    ==> Building track 'TEAM/TRACK_NAME' (ID: TRACK_ID)
    23
    Track URL: https://play.instruqt.com/TEAM/tracks/TRACK_NAME
    24
    OK
    Copied!
    TEAM, TRACK_NAME, and TRACK_ID will be your team, track name, and track id. ↳ As you can see in line 22, the track is automatically re-build as part of the push.
Your track is ready to share now.
Copy link
Edit on GitHub
Contents
Deploy