ToolJet/docs/versioned_docs/version-3.16.0-LTS/setup/try-tooljet.md
Adish M 03e074ad48
docs: Add workflow scheduling instructions and Redis configuration guidance across deployment documentation (#14307)
* Update workflow scheduling instructions across multiple deployment documents

* refactor docs for support new workflow style with redis

* Add warning about whitelisting ToolJet AI features in DigitalOcean and Try ToolJet setup documentation

* Remove "High-Level" from the "How It Works" section title in the migration guide

* Add note about ToolJet version compatibility in migration guide

* Add migration guide reference for users transitioning from Temporal-based workflows

* Update documentation to recommend external Redis for multiple workflow workers across various deployment setups

* Update Docker setup instructions and clarify migration guide version compatibility

* Remove rollback plan section from the Temporal to BullMQ migration guide

* Update documentation to clarify external Redis requirements for multiple worker setups

* Remove TOOLJET_QUEUE_DASH_PASSWORD references from environment variable documentation across multiple setup guides

* Update Redis configuration documentation to clarify external instance requirements and add workflow scheduling variables

* Update migration guide to reflect correct ToolJet version for BullMQ transition
2025-11-12 16:25:56 +05:30

53 lines
1.8 KiB
Markdown

---
id: try-tooljet
title: Try ToolJet
---
# Try ToolJet
:::warning
To use ToolJet AI features in your deployment, make sure to whitelist `https://api-gateway.tooljet.ai` and `https://python-server.tooljet.ai` in your network settings.
:::
## On local with Docker
You can run the command below to have ToolJet up and running right away.
```bash
docker run \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
--platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/16/main \
tooljet/try:ee-lts-latest
```
#### Setup information
- Runs the ToolJet server on the port 80 on your machine.
- Container has postgres already configured within. All the data will be available in the docker volume `tooljet_data`.
- You can make use of `--env` or `--env-file` flag to test against various env configurables mentioned [here](/docs/setup/env-vars).
- Use `docker stop tooljet` to stop the container and `docker start tooljet` to start the container thereafter.
#### Dynamic Port Setup
To run the ToolJet server on a different port, such as 8080 or any other port of your choice, use the following command:
```sh
docker run \
--name tooljet \
--restart unless-stopped \
-p 8080:8080 \
-e PORT=8080 \
--platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/16/main \
tooljet/try:ee-lts-latest
```
- This command will start the ToolJet server on port 8080.
- The `-e PORT=8080` flag sets the `PORT` environment variable to 8080, allowing the ToolJet server to listen on port 8080.
By following these instructions, you can easily run the ToolJet server on the port of your choice, ensuring flexibility in your setup.
_If you have any questions feel free to join our [Slack Community](https://join.slack.com/t/tooljet/shared_invite/zt-2rk4w42t0-ZV_KJcWU9VL1BBEjnSHLCA) or send us an email at support@tooljet.com._