* whtie label revamp * minor changes * updated beta info in copilot docs * renamed gds to ds in overview doc of v2.15 onwards * updated multienv: renamed gds to ds, updated screenshot * updated multienv: app state description * updated superadmin wrt new licensing updates * licensing update: free trial * updates in licensing * changes after review * [docs]updated restapi with bearer auth * Update kubernetes-aks.md * Update openshift.md * Update ecs.md * Update ecs.md * Update kubernetes-gke.md * Update kubernetes.md * Update docker.md * Update docker.md * Update ecs.md * Update google-cloud-run.md * Update kubernetes-aks.md * Update kubernetes-gke.md * Update kubernetes.md * Update openshift.md * Update kubernetes-gke.md * Update kubernetes-aks.md * fixed ecs, removed heroku from 2.15 onwards * updated digitalocean doc * licensing doc changes and location * Update digitalocean.md * Update digitalocean.md * added v2.18.0 --------- Co-authored-by: Adish M <44204658+adishM98@users.noreply.github.com>
3.2 KiB
| id | title |
|---|---|
| client | Deploying ToolJet client |
Deploying ToolJet client
ToolJet client is a standalone application and can be deployed on static website hosting services such as Netlify, Firebase, S3/Cloudfront, etc.
You can build standalone client with the below command:
SERVE_CLIENT=false npm run build
If you have any questions feel free to join our Slack Community or send us an email at hello@tooljet.com.
Deploying ToolJet client on Firebase
:::tip
You should set the environment variable TOOLJET_SERVER_URL ( URL of the server ) while building the frontend and also set SERVE_CLIENT to `false`` for standalone client build.
For example: SERVE_CLIENT=false TOOLJET_SERVER_URL=https://server.tooljet.com npm run build && firebase deploy
:::
- Initialize firebase project
Select Firebase Hosting and set build as the static file directoryfirebase init - Deploy client to Firebase
firebase deploy
Deploying ToolJet client with Google Cloud Storage
:::tip
You should set the environment variable TOOLJET_SERVER_URL ( URL of the server ) while building the frontend.
For example: SERVE_CLIENT=false TOOLJET_SERVER_URL=https://server.tooljet.io npm run build
:::
Using Load balancer
Tooljet client can be hosted from Cloud Storage bucket just like hosting any other static website. Follow the instructions from google documentation here.
Summarising the steps below:
-
Create a bucket and upload files within the build folder such that the
index.htmlis at the bucket root. -
Edit permissions for the bucket to assign New principal as
allUserswith role asStorage Object Viewerand permit for public access for the bucket. -
Click on Edit website configuration from the buckets browser and specify the main page as
index.html -
Follow the instructions on creating a load balancer for hosting a static website.
-
Optionally, create Cloud CDN to use with the backend bucket assigned to the load balancer.
-
After the load balancer is created there will be an IP assigned to it. Try hitting it to check the website is being loaded.
-
Use the load balancer IP as the static IP for the A record of your domain.
Using Google App Engine
-
Upload the build folder onto a bucket
-
Upload
app.yamlfile onto bucket with the following configruntime: python27 api_version: 1 threadsafe: true handlers: - url: / static_files: build/index.html upload: build/index.html - url: /(.*) static_files: build/\1 upload: build/(.*) -
Activate cloud shell on your browser and create build folder
mkdir tooljet-assets -
Copy the uploaded files onto an assets folder which is to be served
gsutil rsync -r gs://your-bucket-name/path-to-assets ./tooljet-assets -
Deploy static assets to be served
cd tooljet-assets && gcloud app deploy