Skip to main content
Version: 3.1.0-Beta 🚧

Deploying ToolJet on Google Cloud Run

info

You should setup a PostgreSQL database manually to be used by ToolJet.

Follow the steps below to deploy ToolJet on Cloud run with gcloud CLI.

Deploying ToolJet application​

  1. Create a new Google Cloud Run Service:
Google Cloud Run New Setup
  1. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit.
ingress-auth
  1. Under containers tab, please make sure the port is set to 3000 and command npm, run, start:prod is entered in container argument field with CPU capacity set to 2GiB:
port-and-capacity-tooljet
  • If the command mentioned above is not compatible, please use the following command structure instead:
port-and-capacity-tooljet-alternative-command
  • Should you encounter any migration issues, please execute the following command. Be aware that executing this command may cause the revision to break. However, modifying the command back to npm, run, start:prod will successfully reboot the instance:
port-and-capacity-tooljet-migration-fix-command
  1. Under environmental variable please add the below ToolJet application variables. You can also refer env variable here.

Update TOOLJET_HOST environment variable if you want to use the default url assigned with Cloud run after the initial deploy.

env-variable-tooljet
tip

If you are using Public IP for Cloud SQL, then database host connection (value for PG_HOST) needs to be set using unix socket format, /cloudsql/<CLOUD_SQL_CONNECTION_NAME>.

  1. Please go to the connection tab. Under Cloud SQL instance please select the PostgreSQL database which you have set-up.
cloud-SQL-tooljet

Click on deploy once the above parameters are set.

info

Once the Service is created and live, to make the Cloud Service URL public. Please follow the steps here to make the service public.

Deploying ToolJet Database​

To use ToolJet Database, you'd have to set up and deploy PostgREST server which helps querying ToolJet Database. Deploying ToolJet Database is mandatory from ToolJet 3.0 or else the migration might break, checkout the following docs to know more about new major version, including breaking changes that require you to adjust your applications accordingly:

  1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific PostgREST image from docker hub and then tag with your project to push it to cloud registry.

    docker pull postgrest/postgrest:v12.0.2

    Please run the above command by launching googleCLI which will help to push the PostgREST image to Google container registry.

  2. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit.

    ingress-auth

  3. Under containers tab, please make sure the port is set 3000 and CPU capacity is set to 1GiB.

    port-and-capacity-postgrest

  4. Under environmental variable please add corresponding ToolJet database env variables. You can also refer env variable.

  5. Please go to connection tab. Under Cloud SQL instance please select the PostgreSQL database which you have set-up for ToolJet application or the separate PostgreSQL database created respective to ToolJet Database from the drop-down option.

    Cloud-SQL-instance

    Click on deploy once the above parameters are set.

    info

    Once the Service is created and live, to make the Cloud Service URL public. Please follow the steps here to make the service public.

  6. Additional Environmental variable to be added to ToolJet application or ToolJet Server connect to PostgREST server. You can also refer env variable here

    env-for-tooljet

Upgrading to the Latest LTS Version​

New LTS versions are released every 3-5 months with an end-of-life of atleast 18 months. To check the latest LTS version, visit the ToolJet Docker Hub page. The LTS tags follow a naming convention with the prefix LTS- followed by the version number, for example tooljet/tooljet:ee-lts-latest.

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 LTS Version:​

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

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

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