-
Notifications
You must be signed in to change notification settings - Fork 289
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
Provide a docker image to make it easy to try Pyston #1096
Comments
I simply made for |
but in my opinion we can do better job with automated build for provide |
+1 for a docker image. Should be pretty easy considering this should already build on Ubuntu (version? precise?). Could just use a base image that starts with that version of Ubuntu and then apt-get anything else that is needed. Also, could use Docker Hub automated builds so dev releases can be tried easily. |
I used Vagrant to build Pyston for a while, this is the Vagrant file I used: https://gist.github.com/aisk/efd38d84575ed7087280 I think we can provide docker and vagrant envs both to let people choose which they want (since use docker in OSX is not straight-forwar), and maintain both of them seems not a hard work. |
for what i can tell an automated build seems out of its resources limits (2h and afair 1GB RAM, 1 CPU and 30GB drive). i suppose a debian package would be a good idea anyway. if that dependency on |
Congrats on your new company! Glad to see this project moving forward 😄 🎉 |
Thanks @jakirkham ! |
Or maybe some other tool (Vagrant was suggested at one point). This gets asked for fairly regularly and I think is appreciated in other projects when available.
We're happy to help out from the Pyston side but if anyone with some experience setting up docker containers wants to give this a go, it would really helpful :)
The text was updated successfully, but these errors were encountered: