A Jupyter Notebook is an open-source web application that allows you to create and share documents that contain live code, equations, visualizations and narrative text.
- data cleaning and transformation
- numerical simulation
- statistical modeling
- data visualization
- machine learning
- and other stuff
I’ve been interested in how to set up a Jupyter Notebook on my Linode server for a while, but kept running into a roadblock (either mental or technical I’m not really sure).
Then I came across this ‘sweet’ solution to get them set up athttp://blog.lerner.co.il/five-minute-guide-setting-jupyter-notebook-server/
My main issue was what I needed to to do keep the Jupyter Notebook running once I disconnected from command line. The solution above gave me what I needed to solve that problem
nohup jupyter notebook
nohup allows you to disconnect from the terminal but keeps the command running in the background (which is exactly what I wanted).
The next thing I wanted to do was to have the
jupyter notebook server run from a directory that wasn’t my home directory.
To do this was way easier than I thought. You just run
nohup jupyter notebook from the directory you want to run it from.
The last thing to do was to make sure that the notebook would start up with a server reboot. For that I wrote a shell script
# change to correct directory
nohup jupyter notebook &> /home/ryan/output.log
The last command is a slight modification of the line from above. I really wanted the output to get directed to a file that wasn’t in the directory that the
Jupyter notebook would be running from. Not any reason (that I know of anyway) … I just didn’t like the
nohup.out file in the working directory.
Anyway, I now have a running Jupyter Notebook at http://python.ryancheley.com:8888
I’ve been futzing around with SSL on this site since last December. I’ve had about 4 attempts and it just never seemed to work.
Earlier this evening I was thinking about getting a second Linode just to get a fresh start. I was this close to getting it when I thought, what the hell, let me try to work it out one more time.
And this time it actually worked.
I’m not really sure what I did differently, but using this site seemed to make all of the difference.
The only other thing I had to do was make a change in the word press settings (from
https) and enable a plugin Really Simple SSL and it finally worked.
I even got an ‘A’ from SSL Labs!
Again, not really sure why this seemed so hard and took so long.
I guess sometimes you just have to try over and over and over again
When I scheduled my last post on December 14th to be published at 6pm that night I noticed that the schedule time was a bit … off:
I realized that the server times as still set to GMT and that I had missed the step in the Linode Getting Started guide to Set the Timezone.
No problem, just found the Guide, went to this section and ran the following command:
sudo dpkg-reconfigure tzdata
I then selected my country (US) and my time zone (Pacific-Ocean) and now the server has the right timezone.
Switching to Linode
I’ve been listening to a lot of Talk Python to me lately … I mean a lot. Recently there was a coupon code for Linode that basically got you four months free with a purchase of a single month, so I thought, ‘what the hell’?
Anyway, I have finally been able to move everything from AWS to Linode for my site and I’m able to publish from my beloved Ulysses.
Initially there was an issue with xmlrpc which I still haven’t fully figured out.
I tried every combination of everything and finally I’m able to publish.
I’m not one to look a gift horse in the mouth so I’ll go ahead and take what I can get. I had meant to document a bit more / better what I had done, but since it basically went from not working to working, I wouldn’t know what to write at this point.
The strangest part is that from the terminal the code I was using to test the issue still returns and xmlrpc faultCode error of -32700 but I’m able to connect now.
I really wish i understood this better, but I’m just happy that I’m able to get it all set and ready to go.
Next task … set up SSL!