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

Consider using shiv instead of virtualenvs for deployment #445

Open
dan-blanchard opened this issue Aug 16, 2018 · 2 comments
Open

Consider using shiv instead of virtualenvs for deployment #445

dan-blanchard opened this issue Aug 16, 2018 · 2 comments

Comments

@dan-blanchard
Copy link
Member

dan-blanchard commented Aug 16, 2018

Shiv is much lighter weight than PEX, which we had previously discussed using in #212. It just uses pip's underlying mechanisms for packaging things up in zipapp, so I'd prefer to use it.

You can see how to use it for cross-platform building in this comment.

@kbourgoin
Copy link
Member

This would be amazing. A big 👍 from me on getting this working. It'd massively simplify deploying to large clusters, not to mention resizing clusters on the fly.

@dan-blanchard
Copy link
Member Author

dan-blanchard commented Dec 6, 2018

Hit an issue with only being able to pass a single command to ShellComponent via Thrift, so I filed STORM-3299. STORM-152 is also annoying, but if I could pass multiple arguments to a script, I could work around it easily.

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

No branches or pull requests

2 participants