df311eeb03
* Enhance ToolJet deployment documentation for version 3.16.0-LTS - Updated Google Cloud Run setup to clarify architecture and environment variables. - Improved Kubernetes setup documentation for AKS, EKS, GKE, and general Kubernetes, emphasizing the need for two separate PostgreSQL databases. - Revised OpenShift deployment instructions to include detailed environment variable configurations and deployment steps. - Added system requirements for PostgreSQL and Redis, specifying recommended versions and minimum specifications. - Included warnings about database naming conflicts and critical configurations for successful deployment. * Enhance upgrade documentation for ToolJet LTS version - Added critical backup reminder for PostgreSQL instance before upgrading. - Clarified database requirements, emphasizing the need for two separate database names (PG_DB and TOOLJET_DB). - Included deployment flexibility options for database hosting. - Updated installation notes to specify that the upgrade guide is only for existing installations. - Improved formatting and clarity in various setup guides (Azure, DigitalOcean, Docker, ECS, Google Cloud Run, Kubernetes, OpenShift). * Enhance deployment documentation for ToolJet on various platforms, including AWS AMI, Azure Container Apps, AWS ECS, Google Cloud Run, Kubernetes (AKS, EKS, GKE), and Openshift. Updated warnings and notes regarding PostgreSQL database setup and ToolJet AI features. * Enhance deployment documentation for ToolJet LTS version 3.16.0 by updating backup instructions, removing redundant version requirements, and clarifying Redis configuration for external instances. * Refine deployment documentation for ToolJet by removing redundant environment variable references and adding notes on securing Redis passwords across various platforms including AWS AMI, Docker, Google Cloud Run, Kubernetes (AKS, EKS, GKE), and OpenShift. * Refine Redis configuration instructions in AWS AMI deployment documentation for clarity and formatting consistency. * Add new environment variables for bulk upload limits in deployment documentation * Refine deployment documentation for ToolJet subpath installation by improving environment variable formatting and clarifying upgrade prerequisites. * Update PostgreSQL database links in deployment documentation for consistency across ECS, Helm, Kubernetes (AKS, EKS, GKE), and OpenShift setups. * Remove warning about whitelisting ToolJet AI features from Helm deployment documentation * Refine environment variable configuration for workflow scheduling in Helm deployment documentation * formatting updates till gke * final formatting updates --------- Co-authored-by: rudrapratik30 <pratik104agrawal@gmail.com>
3.8 KiB
| id | title |
|---|---|
| digitalocean | DigitalOcean |
Follow the steps below to deploy ToolJet on a DigitalOcean Droplet.
:::warning
To use ToolJet AI features in your deployment, make sure to whitelist https://api-gateway.tooljet.com and https://python-server.tooljet.com in your network settings.
:::
1. Navigate to the Droplets section in DigitalOcean.
2. Configure the Droplet with the following options:
- Image: Ubuntu
- Plan: Choose a plan (e.g., Basic, 4GB RAM, 2 vCPU)
- Auth: For authentication, use password or ssh
- Click Create Droplet and note the assigned public IP
3. Create a Firewall for the Droplets to allow required ports:
Required Inbound Firewall Rules
- Port 22 (SSH) - TCP
- Allowed CIDR: Your IP address only
- Purpose: Secure administrative access to the Droplet
- Port 80 (HTTP) - TCP
- Allowed CIDR:
0.0.0.0/0(all sources) - Purpose: Public web access to ToolJet
- Allowed CIDR:
- Port 443 (HTTPS) - TCP
- Allowed CIDR:
0.0.0.0/0(all sources) - Purpose: Secure public web access to ToolJet
- Allowed CIDR:
:::tip For enhanced security, restrict SSH access (port 22) to your specific IP address only. HTTP and HTTPS ports should remain open to all sources for public access to your ToolJet instance. :::
4. Connect to the Droplets via SSH.
5. Install Docker and Docker Compose using the following commands:
apt update && apt upgrade -y
apt install -y docker.io
Enable and start Docker:
systemctl enable docker
systemctl start docker
Install Docker Compose:
apt install -y curl
curl -SL https://github.com/docker/compose/releases/latest/download/docker-compose-linux-x86_64 -o /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose
Verify installation:
docker --version
docker-compose --version
6. Update the TOOLJET_HOST in the .env file:
TOOLJET_HOST=http://<public_ip>:80
7. Use the Docker Documentation to deploy ToolJet.
Upgrading to the Latest LTS Version
:::info If this is a new installation of the application, you may start directly with the latest version. This upgrade guide is only for existing installations. :::
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.
Prerequisites for Upgrading
:::warning Critical: Backup Your PostgreSQL Instance
Before starting the upgrade process, perform a comprehensive backup of your PostgreSQL instance to prevent data loss. Your backup must include both required databases:
- PG_DB (Application Database) - Contains users, apps, and configurations
- TOOLJET_DB (Internal Database) - Contains ToolJet Database feature data
Ensure both databases are included in your backup before proceeding with the upgrade. :::
- Users on versions earlier than v2.23.0-ee2.10.2 must first upgrade to this version before proceeding to the latest LTS version.
---
Need Help?
- Reach out via our Slack Community
- Or email us at support@tooljet.com
- Found a bug? Please report it via GitHub Issues