Updating an Existing Application

In this document, we'll guide you through the process of updating an existing application that is already deployed.


Before proceeding, ensure you have the following prerequisites in place:

  • Tailor CLI installed
  • A Tailor Platform account created
  • A workspace created
  • An application created (If you don't have an application yet, please follow the instructions on Console.)

Prepare Your Local Repository

Begin by either cloning the template repository from our public template repository link, or request the Tailor team to share a custom repository with you if you are using a customized template.

If you already have a working repository, you can skip this step.

Set up the module.cue File

Once you have created an application, you will find a module.cue file in a cue.mod directory within your local repository. The module.cue file defines your cue module name, which will also be your application name.

<span><span style="color: var(--shiki-color-text)">module: </span><span style="color: var(--shiki-color-text)">&quot;</span><span style="color: var(--shiki-token-string-expression)">tailor.build/&lt;your_app_name&gt;</span><span style="color: var(--shiki-color-text)">&quot;</span></span>
<span><span style="color: var(--shiki-color-text)">language: version: </span><span style="color: var(--shiki-color-text)">&quot;</span><span style="color: var(--shiki-token-string-expression)">v0.9.0</span><span style="color: var(--shiki-color-text)">&quot;</span></span>

Open this file using your preferred code editor or Integrated Development Environment (IDE) and ensure that the module name matches the application name displayed in the Console.

Demo screen

In this case, crm-rboqocta is the application name. <your_app_name>.erp.dev will serve as your application's Gateway for sending requests.

If the module name does not match your application name as displayed in the Console, please replace the module name with the name displayed in the Console.

Update the configuration file

Execute the following command in the root directory of your application template within your local repository:

<span><span style="color: var(--shiki-token-function)">tailorctl</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">manifest</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">tidy</span></span>
<span><span style="color: var(--shiki-token-function)">cue</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">eval</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">-f</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">manifest/workspace.cue</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">-o</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">generated/workspace.cue</span></span>

Apply the Template

The generated directory contains application configurations. Apply them to complete the setup:

<span><span style="color: var(--shiki-token-function)">tailorctl</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">workspace</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">apply</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">-m</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">generated/workspace.cue</span></span>

Confirm the deployed app

Open the Console screen and confirm that the application has been deployed.

Further information

Congratulations on successfully updating your application in the Tailor Platform! Here are some additional resources to help you continue your journey: