Automatically build Docker images in case of updates of Pluto.jl or PlutoUI.jl
lungben opened this issue · 11 comments
Currently, the build of Pluto Docker images need to be triggered manually in Dockerhub.
This should be automated using Github Actions.
Great! Do I need to do anything?
Probably you need to set up some credentials for the Git repos to work together with Dockerhub, but I first need to get familiar myself with this topic.
I'll let you know when I need your help.
fyi, the Github actions workflow is already setup with this file
TODO: Need to use a proper convention for version numbering
for Docker Personal Access Token
Dockerhub > Account Settings > Security > New AccessToken
Github project Settings > Secrets > New secret > Name=DOCKER_PAT value=token from above step
@shashankp thanks for the instructions!
fyi, for Binder, the plutojl/pluto-binder docker image need to have a version# as tag, latest wouldnt work
This would work in local, but for Binder
docker run -it -p 8080:8080 plutojl/pluto-binder:latest jupyter notebook --ip=0.0.0.0 --port=8080
Thanks for the information, I tagged the latest version with 0.1.
adding dockerfile will make a git repo with Pluto notebooks work in binder & also Jupyter in local
Badge link
Can add this to wiki?
The bindered Pluto has securty enabled, and doesn't allow /open?url=... links:
https://mybinder.org/v2/gh/shashankp/18S191/master?urlpath=pluto/open?url=https%253A%252F%252Fgist.githubusercontent.com%252Ffonsp%252Fd88b3adc8c958dce780cf7c4df8fa437%252Fraw%252F2a8a5bdc6d8b1bcb4462006f62ead2f52fec17bf%252Fturtles.jl
Silly question... where do I find plutojl/pluto-binder?
Maybe not directly in the url, but in here
But we want it directly from the URL! http://pluto-on-binder.glitch.me/
@fonsp Could you please do the steps described by @shashankp ?
You need your Dockerhub and Github account for this.
TODO: Need to use a proper convention for version numbering
for Docker Personal Access Token
Dockerhub > Account Settings > Security > New AccessToken
Github project Settings > Secrets > New secret > Name=DOCKER_PAT value=token from above step
As far as I can see, the automatic creation of Docker images and the CI pipeline in general should work after the tokens are set.