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
Docker image generation #1484
Docker image generation #1484
Conversation
I will still need to add documentation, but this branch should be merged with master before we modify circle.yml. |
# http://3ofcoins.net/2013/09/22/flat-docker-images/ | ||
# | ||
# TODO: replace with something homemade | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add the Boost License header
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
U sure? We don't even have the copyright for this file, I pulled it in from that dude. He published it via gist without copyright note
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
He added his copyright but published it without a license (which means it's in the public domain). That entitles us to relicense it under the Boost license, I don't see a problem with that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, technically he didn't even add his name in, I did that ;)
Should I strip his name out? Or is it polite to leave that in
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd leave his copyright in place, credit where credit is due...
LGTM, please go ahead and merge. |
This branch will create a docker image with hpx installed on it.
This could be used for rapid prototyping, external unit tests, writing minimal examples that reproduce errors, potential deployment in the cloud, continuous integration for external projects (like hpxcl), etc.