Skip to content
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

[Feature]: Docker image #39

Closed
bizk opened this issue Sep 15, 2023 · 0 comments · Fixed by #37
Closed

[Feature]: Docker image #39

bizk opened this issue Sep 15, 2023 · 0 comments · Fixed by #37
Assignees
Labels

Comments

@bizk
Copy link
Contributor

bizk commented Sep 15, 2023

Summary

It is beneficial for the project to have a docker image that can be used by the users and developers. Making it easy to deploy and lowering the adoption bar.

Problem Definition

The following reasons to use a docker container:

  • Isolation: Docker containers provide a controlled environment for applications. The image ensures that all required dependencies and tools are packaged together, reducing compatibility issues.
  • Portability: Docker images are portable across different environments. Making it easier to deploy and run the Rosetta service consistently on various platforms without worrying about misconfiguration or dependency issues.

Problems addressed:

  • Ease of Deployment: Having a container makes setting up and using Rosetta easier across all platforms.
  • E2E and integration testing: It allows us to make better and meaningful E2E/integration tests.

Benefits for the SDK:

  • Simplified Setup: Anyone who desires to use Rosetta can use it as a plug and play through docker.

Proposal

Create a docker image that builds rosetta and it's default plugin. And add a the respective github workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant