Skip to main content
Version: 2.1.0

Deploying ToolJet on Azure container apps

info

Please note that you need to set up a PostgreSQL database manually to be used by ToolJet

If you have any questions feel free to join our Slack Community or send us an email at [email protected].

Deploying ToolJet application

  1. Open the Azure dashboard at https://portal.azure.com, navigate to Container Apps, and click on "Create container app".
Deploying ToolJet on Azure container apps
  1. Select the appropriate subscription and provide basic details such as the container name.
Deploying ToolJet on Azure container apps
  1. In the container tab, uncheck the "Use quickstart image" option to select the image source manually.
Deploying ToolJet on Azure container apps
  • Make sure to provide the image tag, and then enter npm run start:prod in the "Command override" field.
  • Add the following ToolJet application variables under the "Environmental variable" section. You can refer to this documentation for more information on environment variables.
Deploying ToolJet on Azure container apps
  1. In the ingress tab, configure Ingress and Authentication settings as shown below. You can customize the security configurations as per your requirements. Make sure the port is set to 3000.
Deploying ToolJet on Azure container apps
  1. Click on "Review + create" and wait for the template to be verified and passed, as shown in the screenshot below.
Deploying ToolJet on Azure container apps
  1. Once the container is deployed, you can verify its status under revision management.
Deploying ToolJet on Azure container apps

You can access ToolJet via the application URL provided in the overview tab.

Upgrading to the Latest Version

The latest version includes architectural changes and, hence, comes with new migrations.

If this is a new installation of the application, you may start directly with the latest version. This guide is not required for new installations.

Prerequisites for Upgrading to the Latest Version:

  • It is crucial to perform a comprehensive backup of your database before starting the upgrade process to prevent data loss.

  • Ensure that your current version is v2.23.0-ee2.10.2 before upgrading.

  • Users on versions earlier than v2.23.0-ee2.10.2 must first upgrade to this version before proceeding to the latest version.

For specific issues or questions, refer to our Slack.