ToolJet/docs/versioned_docs/version-2.15.0/setup/azure-container.md

id	title
azure-container	Azure container apps

Deploying ToolJet on Azure container apps

:::info Please note that you need to set up a PostgreSQL database manually to be used by ToolJet. Additionally, you must set up a Redis service through Azure Cache for Redis. :::

If you have any questions feel free to join our Slack Community or send us an email at hello@tooljet.com.

Deploying ToolJet application

1. Open the Azure dashboard at https://portal.azure.com, navigate to Container Apps, and click on "Create container app".

2. Select the appropriate subscription and provide basic details such as the container name.

3. In the container tab, uncheck the "Use quickstart image" option to select the image source manually.

• 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.

Note: For the minimal setup, ToolJet requires: TOOLJET_HOST, PG_HOST, PG_DB, PG_USER, PG_PASSWORD, SECRET_KEY_BASE & LOCKBOX_MASTER_KEY keys in the secret.

4. 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.

5. Click on "Review + create" and wait for the template to be verified and passed, as shown in the screenshot below.

6. Once the container is deployed, you can verify its status under revision management.

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

Upgrading to v2.24.3-ee2.10.2

Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.

If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. 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.3-ee2.10.2 before upgrading.

• Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.

For specific issues or questions, refer to our Slack.