-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DevService: Start Temporal stack #17
Comments
👍 could be nice ! |
@ggrebert any help would be appreciated! Thank you so much for the GRPC fix! |
with pleasure. For the docker-compose, the default one seems to be too large (pg + elasticsearch + temporal) What to you think about the MySQL one? |
I am OK with whatever one works. I didn't know if we would have to turn that Docker Compose into a single container on DockerHub to make it work with TestContainers? |
We should:
|
I absolutely love this idea. |
It's very nice to see you collaborating on this! |
I asked the Temporal Slack I've been working on a new project using Temporal after the success of the previous production deployment of the initial application and find it would be really awesome to have a Temporal spin up automatically, especially for anyone not really versed in Temporal server setup themselves and just want a quick way to test their code. If you haven't joined their channel, I recommend it. They are very active and good group of people. https://temporalio.slack.com/archives/CTT84KXK9/p1738627889685729 This is my message:
|
I got a response back from Temporal's advocate Tihomir Surdilovic and he mentioned the following:
|
Basically start a Dev Service stack using someting like that docker compose stack:
https://github.com/temporalio/docker-compose
This will give it a true Quarkus feel.
sqlite
The text was updated successfully, but these errors were encountered: