Skip to content

Conversation

imaginator
Copy link

I've created the following files:

Dockerfile.c
Dockerfile.haskell
Dockerfile.coq

Builds are now self contained and drops the user into either a ghci or coq prompt. Ideally we could publish these containers to Dockerhub which would make it easier for experimenting [without waiting for long builds].

The README.md needs a bit of a rework too, but that's another project.

@apoelstra
Copy link
Contributor

I will go ahead and run my local CI on this, though I checked that no existing source files are changed. I don't have docker installed on any of my systems and I'm not really familiar with the syntax or what these containers are supposed to do.

Copy link
Contributor

@apoelstra apoelstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK fc1f8a2; successfully ran local tests

@imaginator
Copy link
Author

@apoelstra their use is documented in the README.md file. For example the building and running the Coq version should give a coqtop prompt with everything built. Likewise, the haskell image presents a GHCi console with correct Simplicity modules loaded. (6892b08)

My thinking behind these is that it makes an easy way to write tutorials and, like with Nix images, present users with all the dependencies they need to get experimenting with Simplicity quickly.

Copy link
Contributor

@apoelstra apoelstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 6892b08; successfully ran local tests

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

Successfully merging this pull request may close these issues.

2 participants