[cli] Add a tool to run locally an application on docker #393
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eolivelli
changed the title
eolivelli
changed the title
| Files.write(tmpInstanceFile.toPath(), instanceContents.getBytes(StandardCharsets.UTF_8)); | ||
| File tmpSecretsFile = Files.createTempFile("secrets", ".yaml").toFile(); | ||
| Files.write(tmpSecretsFile.toPath(), secretsContents.getBytes(StandardCharsets.UTF_8)); | ||
| String imageName = "langstream/langstream-runtime-tester:latest-dev"; |
There was a problem hiding this comment.
we should make this configurable
There was a problem hiding this comment.
probably in this case it's better to push a "latest" for the runtime-tester image?
There was a problem hiding this comment.
this should be configurable and it should use "some release", ideally the same version of the CLI
|
I am committing this first part of the PR. |
benfrank241
pushed a commit
to vectorize-io/langstream
that referenced
this pull request
May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goals:
allow users to quickly iterate over the configurations without needing to deploy the application to a kubernetes cluster
Summary:
How to run the tool:
bin/langstream docker run -app /path/to/app -i /path/to/instance -s /path/to-secrets --start-broker=true|false --start-s3=true|falseit is the same command as "apps deploy" but you use "local-run" instead of "deploy".
As the environment is ephemeral you must always pass the instance.yaml and the secrets.yaml files
By default we also start Kafka and Minio, you can control them by using --start-broker and --start-s3
Limitations of the "local mode":