Can users edit the notebooks on a public notebook server?

Question

I'm considering IPython notebook for educational purposes. The idea is to provide the students with webbased demos that illustrate some topics of the lecture. I'd like the students to be able to change the parameters of the code so that they can study their impact or even create their own examples.

I've learned that it is possible to setup a public Ipython notebook server. As I understand it, it provides the full functionality of notebooks (not just displaying them) but exposed to the public. Is that right?

Bonus question: how can I prevent users from persistently changing the notebooks but provide the with a "session copy"?

Answer 1

As for the second point, I have a working setup on my local machine. I haven't tested it on a server, so your mileage may vary. Simple solution: I made the *.ipynb file read-only. A quick test showed me that I can access it through the online notebook, make modifications, run the code, try to save ("notebook save failed"), download the modified file as a *.ipynb file since saving didn't work, and carry on from another local notebook. I hope this matches your use-case.

Edit: I feel I should clarify the behaviour a bit. Basically, each user has their temporary session which persists pretty much until they navigate away from the page. If this is in a university lecture-hall, I'm sure you'll hear the occasional "Oh &%$#!" when someone closes their browser by mistake, but the notebook does prompt before allowing you to navigate away, so I feel that this should be fairly rare. Once they navigate away from the page, all their work is gone. I think this fulfills the criteria for a non-persistant session copy.

Answer 2

1. Yes, that's right. A public iPython notebook server provides the full funcionality to everyone who connects to it via a browser. So everyone who has the server's password can edit/create/delete notebooks on this server.

2. As far as I know, there's no possibility to prevent users from persistently changing the notebooks on the server. A dirty workaround would be: Every student copies your central notebook (File --> Make a copy) and works in the copied notebook only. This, however, doesn't prevent abuse/unintentional changes by the students in the central notebook.