diff --git a/docs/docs/how-to/run-action-from-runjs.md b/docs/docs/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/docs/how-to/run-action-from-runjs.md +++ b/docs/docs/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]` diff --git a/docs/docs/setup/google-cloud-run.md b/docs/docs/setup/google-cloud-run.md index 77387869b6..f0df423cef 100644 --- a/docs/docs/setup/google-cloud-run.md +++ b/docs/docs/setup/google-cloud-run.md @@ -15,40 +15,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application +1. Create a new Google Cloud Run Service: -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +
+ Google Cloud Run New Setup +
-*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* - -```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - - Please run the above command by launching GoogleCLI which will help to push the ToolJet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed ToolJet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
-4. 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: +3. 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 @@ -67,7 +46,7 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. port-and-capacity-tooljet-migration-fix-command
-5. Under environmental variable please add the below ToolJet application variables. You can also refer env variable [**here**](/docs/setup/env-vars). +4. Under environmental variable please add the below ToolJet application variables. You can also refer env variable [**here**](/docs/setup/env-vars). Update `TOOLJET_HOST` environment variable if you want to use the default url assigned with Cloud run after the initial deploy. @@ -80,7 +59,7 @@ If you are using [Public IP](https://cloud.google.com/sql/docs/postgres/connect- ::: -6. Please go to the connection tab. Under Cloud SQL instance please select the PostgreSQL database which you have set-up. +5. Please go to the connection tab. Under Cloud SQL instance please select the PostgreSQL database which you have set-up.
cloud-SQL-tooljet @@ -93,10 +72,6 @@ Click on deploy once the above parameters are set. Once the Service is created and live, to make the Cloud Service URL public. Please follow the steps [**here**](https://cloud.google.com/run/docs/securing/managing-access) to make the service public. ::: - - - - ### Deploying ToolJet Database If you intend to use this feature, you'd have to set up and deploy PostgREST server which helps querying ToolJet Database. diff --git a/docs/static/img/cloud-run/google-cloud-run-setup.png b/docs/static/img/cloud-run/google-cloud-run-setup.png new file mode 100644 index 0000000000..87826a5eea Binary files /dev/null and b/docs/static/img/cloud-run/google-cloud-run-setup.png differ diff --git a/docs/versioned_docs/version-1.x.x/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-1.x.x/how-to/run-action-from-runjs.md index fe7ca8ce70..8b418e3fec 100644 --- a/docs/versioned_docs/version-1.x.x/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-1.x.x/how-to/run-action-from-runjs.md @@ -160,7 +160,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.0.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.0.0/how-to/run-action-from-runjs.md index f2eb6b2dbe..3af2ac54fe 100644 --- a/docs/versioned_docs/version-2.0.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.0.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.1.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.1.0/how-to/run-action-from-runjs.md index 256f9e92d8..5d5b46cbda 100644 --- a/docs/versioned_docs/version-2.1.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.1.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.10.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.10.0/how-to/run-action-from-runjs.md index 40c5272219..1688999519 100644 --- a/docs/versioned_docs/version-2.10.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.10.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.11.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.11.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.11.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.11.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.12.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.12.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.12.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.12.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.13.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.13.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.13.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.13.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.14.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.14.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.14.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.14.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.15.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.15.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.15.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.15.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.16.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.16.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.16.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.16.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.17.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.17.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.17.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.17.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.18.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.18.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.18.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.18.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.18.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.18.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.18.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.18.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.19.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.19.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.19.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.19.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.19.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.19.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.19.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.19.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.2.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.2.0/how-to/run-action-from-runjs.md index e486825316..c32d9062fa 100644 --- a/docs/versioned_docs/version-2.2.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.2.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.22.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.22.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.22.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.22.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.22.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.22.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.22.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.22.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.23.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.23.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.23.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.23.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.23.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.23.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.23.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.23.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.24.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.24.0/how-to/run-action-from-runjs.md index 9fd47278a0..1f637fab87 100644 --- a/docs/versioned_docs/version-2.24.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.24.0/how-to/run-action-from-runjs.md @@ -172,7 +172,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.24.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.24.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.24.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.24.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.25.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.25.0/how-to/run-action-from-runjs.md index 3f52ff2a21..e9e2cd29f5 100644 --- a/docs/versioned_docs/version-2.25.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.25.0/how-to/run-action-from-runjs.md @@ -206,7 +206,7 @@ actions.goToApp('slug', queryparams) ``` - `slug` can be found in the URL of the released app after the `application/`, or in the `Share` modal. You can also set a custom slug for the app in the `Share` modal or from the global settings in the app builder. -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]`. +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`. - Only the apps that are released can be accessed using this action.
diff --git a/docs/versioned_docs/version-2.25.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.25.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.25.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.25.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.27.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.27.0/how-to/run-action-from-runjs.md index 3f52ff2a21..e9e2cd29f5 100644 --- a/docs/versioned_docs/version-2.27.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.27.0/how-to/run-action-from-runjs.md @@ -206,7 +206,7 @@ actions.goToApp('slug', queryparams) ``` - `slug` can be found in the URL of the released app after the `application/`, or in the `Share` modal. You can also set a custom slug for the app in the `Share` modal or from the global settings in the app builder. -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]`. +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`. - Only the apps that are released can be accessed using this action.
diff --git a/docs/versioned_docs/version-2.27.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.27.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.27.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.27.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.29.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.29.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.29.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.29.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.29.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.29.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.29.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.29.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.3.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.3.0/how-to/run-action-from-runjs.md index 5ed45adda6..8e33aa8835 100644 --- a/docs/versioned_docs/version-2.3.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.3.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.30.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.30.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.30.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.30.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.30.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.30.0/setup/google-cloud-run.md index bd638e004b..d6a6e38c9f 100644 --- a/docs/versioned_docs/version-2.30.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.30.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.33.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.33.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.33.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.33.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.33.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.33.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.33.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.33.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.34.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.34.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.34.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.34.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.34.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.34.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.34.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.34.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.35.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.35.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.35.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.35.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.35.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.35.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.35.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.35.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.36.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.36.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.36.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.36.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.36.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.36.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.36.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.36.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.39.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.39.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.39.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.39.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.39.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.39.0/setup/google-cloud-run.md index c486d40881..fdc283a6ce 100644 --- a/docs/versioned_docs/version-2.39.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.39.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.4.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.4.0/how-to/run-action-from-runjs.md index 5ec3faebe5..c0622c1565 100644 --- a/docs/versioned_docs/version-2.4.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.4.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.43.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.43.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.43.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.43.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.43.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.43.0/setup/google-cloud-run.md index ac7fda516f..cb0f3120b2 100644 --- a/docs/versioned_docs/version-2.43.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.43.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the Tooljet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed Tooljet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.5.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.5.0/how-to/run-action-from-runjs.md index 54a7b6d597..e28c7be77a 100644 --- a/docs/versioned_docs/version-2.5.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.5.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.50.0-LTS/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.50.0-LTS/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.50.0-LTS/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.50.0-LTS/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.50.0-LTS/setup/google-cloud-run.md b/docs/versioned_docs/version-2.50.0-LTS/setup/google-cloud-run.md index 92f322cfff..5469502651 100644 --- a/docs/versioned_docs/version-2.50.0-LTS/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.50.0-LTS/setup/google-cloud-run.md @@ -15,38 +15,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application +1. Create a new Google Cloud Run Service: -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +
+ Google Cloud Run New Setup +
-```bash -gcloud auth configure-docker -docker pull tooljet/tooljet:EE-LTS-latest -docker tag tooljet/tooljet:EE-LTS-latest gcr.io//tooljet/tooljet:EE-LTS-latest -docker push gcr.io//tooljet/tooljet:EE-LTS-latest -``` - - Please run the above command by launching GoogleCLI which will help to push the ToolJet application 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.
- CLI + ingress-auth
- -2. Create new cloud run service - - Select and add the pushed ToolJet application image as shown below. - -
- tooljet-app-service -
- -3. 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 -
- -4. 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: +3. 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 @@ -65,7 +46,7 @@ docker push gcr.io//tooljet/tooljet:EE-LTS-latest port-and-capacity-tooljet-migration-fix-command
-5. Under environmental variable please add the below ToolJet application variables. You can also refer env variable [**here**](/docs/setup/env-vars). +4. Under environmental variable please add the below ToolJet application variables. You can also refer env variable [**here**](/docs/setup/env-vars). Update `TOOLJET_HOST` environment variable if you want to use the default url assigned with Cloud run after the initial deploy. @@ -78,7 +59,7 @@ If you are using [Public IP](https://cloud.google.com/sql/docs/postgres/connect- ::: -6. Please go to the connection tab. Under Cloud SQL instance please select the PostgreSQL database which you have set-up. +5. Please go to the connection tab. Under Cloud SQL instance please select the PostgreSQL database which you have set-up.
cloud-SQL-tooljet diff --git a/docs/versioned_docs/version-2.6.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.6.0/how-to/run-action-from-runjs.md index 13b4772705..db46d2ad3e 100644 --- a/docs/versioned_docs/version-2.6.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.6.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.61.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.61.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.61.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.61.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.61.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.61.0/setup/google-cloud-run.md index 15a3b3ed03..e9a9075748 100644 --- a/docs/versioned_docs/version-2.61.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.61.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the ToolJet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed ToolJet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.62.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.62.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.62.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.62.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.62.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.62.0/setup/google-cloud-run.md index 15a3b3ed03..e9a9075748 100644 --- a/docs/versioned_docs/version-2.62.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.62.0/setup/google-cloud-run.md @@ -16,37 +16,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +1. Create a new Google Cloud Run Service: -*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* +
+ Google Cloud Run New Setup +
-```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - Please run the above command by launching GoogleCLI which will help to push the ToolJet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed ToolJet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
+ 4. 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:
diff --git a/docs/versioned_docs/version-2.65.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.65.0/how-to/run-action-from-runjs.md index c0031c4446..497c31084c 100644 --- a/docs/versioned_docs/version-2.65.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.65.0/how-to/run-action-from-runjs.md @@ -225,7 +225,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after `application/` or in the share modal that opens up when you click on the `Share` button on the top-right of the app-builder -- `queryparams` can be provided in this format - `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided in this format - `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.65.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.65.0/setup/google-cloud-run.md index 77387869b6..f0df423cef 100644 --- a/docs/versioned_docs/version-2.65.0/setup/google-cloud-run.md +++ b/docs/versioned_docs/version-2.65.0/setup/google-cloud-run.md @@ -15,40 +15,19 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. ## Deploying ToolJet application +1. Create a new Google Cloud Run Service: -1. Cloud Run requires prebuilt image to be present within cloud registry. You can pull specific tooljet image from docker hub and then tag with your project to push it to cloud registry. +
+ Google Cloud Run New Setup +
-*Ensure you change `replace-with-your-project-id` in the below command with your project ID.* - -```bash - gcloud auth configure-docker - docker pull tooljet/tooljet:EE-LTS-latest - docker tag tooljet/tooljet:EE-LTS-latest gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest - docker push gcr.io/replace-with-your-project-id/tooljet/tooljet:EE-LTS-latest -``` - - Please run the above command by launching GoogleCLI which will help to push the ToolJet application image to Google container registry. - -
- CLI -
- - -2. Create new cloud run service - - Select and add the pushed ToolJet application image as shown below. - -
- tooljet-app-service -
- -3. Ingress and Authentication can be set as shown below, to begin with. Feel free to change the security configurations as per you see fit. +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
-4. 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: +3. 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 @@ -67,7 +46,7 @@ Follow the steps below to deploy ToolJet on Cloud run with `gcloud` CLI. port-and-capacity-tooljet-migration-fix-command
-5. Under environmental variable please add the below ToolJet application variables. You can also refer env variable [**here**](/docs/setup/env-vars). +4. Under environmental variable please add the below ToolJet application variables. You can also refer env variable [**here**](/docs/setup/env-vars). Update `TOOLJET_HOST` environment variable if you want to use the default url assigned with Cloud run after the initial deploy. @@ -80,7 +59,7 @@ If you are using [Public IP](https://cloud.google.com/sql/docs/postgres/connect- ::: -6. Please go to the connection tab. Under Cloud SQL instance please select the PostgreSQL database which you have set-up. +5. Please go to the connection tab. Under Cloud SQL instance please select the PostgreSQL database which you have set-up.
cloud-SQL-tooljet @@ -93,10 +72,6 @@ Click on deploy once the above parameters are set. Once the Service is created and live, to make the Cloud Service URL public. Please follow the steps [**here**](https://cloud.google.com/run/docs/securing/managing-access) to make the service public. ::: - - - - ### Deploying ToolJet Database If you intend to use this feature, you'd have to set up and deploy PostgREST server which helps querying ToolJet Database. diff --git a/docs/versioned_docs/version-2.7.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.7.0/how-to/run-action-from-runjs.md index 314663418e..cbabf71e78 100644 --- a/docs/versioned_docs/version-2.7.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.7.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.8.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.8.0/how-to/run-action-from-runjs.md index 87ea0c9c48..2e76cf150d 100644 --- a/docs/versioned_docs/version-2.8.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.8.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.9.0/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.9.0/how-to/run-action-from-runjs.md index f813840b88..e7b365e12a 100644 --- a/docs/versioned_docs/version-2.9.0/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.9.0/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versioned_docs/version-2.9.4/how-to/run-action-from-runjs.md b/docs/versioned_docs/version-2.9.4/how-to/run-action-from-runjs.md index 1e1152afa7..aad72e317c 100644 --- a/docs/versioned_docs/version-2.9.4/how-to/run-action-from-runjs.md +++ b/docs/versioned_docs/version-2.9.4/how-to/run-action-from-runjs.md @@ -168,7 +168,7 @@ actions.goToApp('slug',queryparams) ``` - `slug` can be found in URL of the released app after the `application/`, or in the `Share` modal -- `queryparams` can be provided like this `[{"key":"value"}, {"key2":"value2"}]` +- `queryparams` can be provided like this `[ ['key1','value1' ], ['key2','value2'] ]`
diff --git a/docs/versions.json b/docs/versions.json index 43c68597c5..c77674550d 100644 --- a/docs/versions.json +++ b/docs/versions.json @@ -3,28 +3,5 @@ "2.62.0", "2.61.0", "2.50.0-LTS", - "2.43.0", - "2.39.0", - "2.36.0", - "2.35.0", - "2.34.0", - "2.33.0", - "2.30.0", - "2.29.0", - "2.27.0", - "2.25.0", - "2.24.0", - "2.23.0", - "2.22.0", - "2.19.0", - "2.18.0", - "2.17.0", - "2.16.0", - "2.15.0", - "2.14.0", - "2.13.0", - "2.12.0", - "2.11.0", - "2.10.0", "1.x.x" ]