Of course, there was a typo, so I had to fix it in my repository, push it back to GitHub, and then repeat the three commands above. I didn’t use the -d option on the docker-compose up because I wanted to see the logs right away in case there was an error in the configuration. Once there, I changed the directory to phpappprod, which contains a clone of the repository, and ran the following: sudo docker-compose down git pull sudo docker-compose up
The name of the service (jupyter) becomes the hostname for the Nginx process that is started by the same docker-compose.yml file, so Nginx can access it as Once those changes were in place, I could commit and push them back to GitHub and then I needed to go to my GCP VM that hosts my PHP demo app. That was a relatively straightforward task of translating the Docker command: jupyter: image: jupyter/scipy-notebook:2c80cf3537ca volumes:. Next, I had to add the Jupyter server to my docker-compose.yml. You’ll have to go back to my previous article to learn exactly how all of this works, but it provides me with single sign-on and HTTPS termination at the Nginx level so the applications don’t need to worry about that. So I created a little script to start it up: docker run -p 8888:8888 -v $
The scipy-notebook seemed to have all the things that were installed for the purposes of the article.
0 kommentar(er)
