bdfe3270e2
* docs: jira * docs: formatting + Client Credentials grant type * docs: connection string pgsql * docs: parameterized queries mysql * docs: parameterized queries in PostgreSQL * docs: update mysql example * docs: TJDB sql editor * docs: add metadata to REST API * docs: add, update postgresql media * docs: add metadata to graphql * docs: update parameterized queries * docs: add parameterized queries for mssql * docs: add SSL Cert to mysql * docs: TJDB SQL restricted commands * docs: update JIRA token location * docs: update delete issue example * docs: update find user by query example * docs: remove session id from get assignable users * docs: use correct image for get issues for board * docs: update create issue example * docs: update delete issue media * docs: update assignable users media * docs: update examples * docs: update key desc * docs: v2.68.0-Beta
1.6 KiB
| id | title |
|---|---|
| tooljet-subpath | Deploying ToolJet on a subpath |
ToolJet can now be deployed at a subpath rather than the root (/) of a public domain. Example subpath installation URL: http://www.yourcompany.com/apps/tooljet
If you have any questions feel free to join our Slack Community or send us an email at hello@tooljet.com.
You'll need to setup the following environment variables if ToolJet installation is on a domain subpath:
| variable | value |
|---|---|
| TOOLJET_HOST | the public URL ( eg: https://www.yourcompany.com ) |
| SUB_PATH | Set a subpath to this variable. The subpath is to be set with trailing / and is applicable only when the server is serving the frontend client. ( eg: /apps/tooljet/ ) |
:::info See all Environment Variables here. :::
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.