That pull request has aged out as the notebook is now version 0.11.4. However, I have refactored things to work with 0.11.4 and sage post 6.4. This is now accessible in my git repository https://github.com/gutow/sagenb_slickgrid in the branch merge_11_4. I have not merged with my master because I haven't finished testing. However, in case others want to test here are instructions for doing it.
0.5) If you do not have git installed on your machine install it. 1) clone my git repository to a directory in the same account as your test sage instance runs from (eg. "git clone https://github.com/gutow/sagenb_slickgrid.git";). 2) navigate to the cloned repository and issue the command "git branch merge_11_4" to switch to the correct branch of the repository. 3) cd to "local/lib/python/site-packages/sagenb*" in your sage install. This should put you inside your sagenb egg. 4) rename the sagenb directory you find there to something else (eg. "mv sagenb sagenb_old"). 5) create a symbolic link with the absolute path to the my repository (eg. "ln -s /home/<sage account>/sagenb_slickgrid/sagenb sagenb") to replace the old sagenb directory. Now when you start sage it will use the updated version of the notebook which should handle proxying properly. I suggest reading the documentation for the notebook command, which I tried to update to explain the proper usage of the proxying. See in particular notes on the 'site_name' parameter. You get this documentation with the sage command "notebook?". Hope this helps. Also, if others look at this I am more likely to be able to find all the bugs that need to be squashed. Jonathan On Wednesday, August 26, 2015 at 9:20:28 PM UTC-5, kcrisman wrote: > > > I can verify that the version of the notebook in sage-6.8 does not support >> proper proxying. I don't have much time to devote to it, but will see if I >> can determine what happened to the code I submitted. It appears that I may >> have the only version of sage running this properly. I can probably make >> my git repository available with instructions on how to replace the >> notebook without proxy support with one that does. >> >> > Jonathan, can I confirm that it would only be your code at > https://github.com/sagemath/sagenb/pull/328 that would be necessary? If > someone else (such as Michael or one of the original posters!) can test > this then I think we could merge that in sagenb proper, which I agree would > be very nice. > > If I recall correctly, I know nothing about proxying and so couldn't > review it with integrity, and there was a semi-important issue of a number > of changed paths to things like published worksheets which could cause > problems in some circumstances (such as published links on other pages or > even in published dead tree articles!). > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
