Self hosting without Temporal

💬 Self Hosted Retool
1

My goal: Self-hosting Retool with workflows and without Temporal.

Issue: Unsure how to configure this.

I am following the docs on to self host Retool. In the section on Temporal, in the self-host tab, you mention:

Retool recommends using a separate datastore for the Workflows Queue in production. Consider using AWS Aurora Serverless V2 configured to an ACU (cpu) provision ranging from 0.5 to 8 ACU. 1 ACU can provide around 10 QPS. The Workflows Queue is write-heavy (around 100:1 write to read operations) and Aurora Serverless can scale to accommodate spikes in traffic without any extra configuration.

.

I have commented out the include block in compose.yml. However, when it comes to the docker.env I am unsure what to set in the environment variables to point the workflows at my Aurora db.

I have tried commenting out: WORKFLOW_TEMPORAL_CLUSTER_FRONTEND_HOST and WORKFLOW_TEMPORAL_CLUSTER_FRONTEND_PORT and setting the WORKFLOW_BACKEND_HOST to the URL of the Aurora db I am using. Am I missing something?

3

Hey @mdeo - I think you are misunderstanding that particular section of our documentation, because Temporal is required in order to utilize workflows. If you are running a cluster locally, it will store the queue in your instance's primary DB unless you point it elsewhere using these environment variables. For use cases requiring particularly high throughput, we recommend using a dedicated DB.

I hope that makes sense! Let me know if you have any additional questions or want to explore spinning up your own Temporal cluster.