Elgato_dark/ToolJet
1
0
Fork 0
mirror of https://github.com/ToolJet/ToolJet synced 2026-05-05 22:38:48 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Merge pull request #12347 from ToolJet/fix/ec2-upgrade-doc

Browse source 
Elaborate the upgrade process for AWS EC2 AMI
This commit is contained in:
Adish M 2025-03-24 14:42:57 +05:30 committed by GitHub
commit a4ffdf81e2
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 32 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

35
docs/versioned_docs/version-3.0.0-LTS/setup/ec2.md
View file

@ -88,15 +88,44 @@ You can learn more about this feature [here](/docs/tooljet-db/tooljet-database).
## Upgrading to the Latest LTS Version
:::note
Users on versions earlier than **v2.23.0-ee2.10.2** must first upgrade to this version before proceeding to the 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](https://hub.docker.com/r/tooljet/tooljet/tags) 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:
#### Steps to Upgrade:
- It is crucial to perform a **comprehensive backup of your database** before starting the upgrade process to prevent data loss.
**1. Backup Your Data**
- Perform a comprehensive backup of your PostgreSQL database 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.
**2. Copy the .env File from the old Instance**
- Before stopping the old instance, copy the `.env` file and store it safely.
**3. Stop the old EC2 Instance**
- To prevent conflicts, stop the old EC2 instance before proceeding with the new deployment.
- Ensure that the old instance remains stopped while setting up the new one.
**4. Launch a New EC2 Instance with the Latest AMI**
- Go to the AWS EC2 dashboard and find the latest ToolJet AMI.
- Launch a new EC2 instance using this AMI.
- Configure security group rules as needed.
**5. Transfer the .env File to the New Instance**
- Upload the saved `.env` file to the appropriate directory on the new instance.
**6. Start the Application**
- SSH into the new instance, navigate to the app directory, and run the setup script:
```bash
cd ~/app
./setup_app
```
**7. Terminate the Old EC2 Instance**
- After verifying that ToolJet is running correctly on the new instance, terminate the old EC2 instance to avoid unnecessary costs.
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*