jonathan's profile - activity

This may be tough one. The issue relates to where the scratch files are put by the server, how the location is passed to the browser and restrictions on cross server scripting. This may get better as I get the javascript version of 3-D plotting working, but I will also keep it in mind and look for other solutions. No promises of rapid progress, the javascript plotting is higher priority.

At this point all I can tell you is that Apple keeps changing exactly how Safari handles Java applets. Sometimes it works, sometimes it doesn't. Things haven't been stable long enough for me to figure out what is going on. We are working on a live non-java 3-D viewer that I hope to have working in Sage this summer. Java is still faster and more responsive, but Apple and Microsoft seem to be trying hard to squash Java. I have not got a definite workaround at this point. You can try Firefox. What I know works is Chromium and FireFox under Linux, where you can actually install Java without the OS trying to override your settings. You can also try adjusting the security level to medium in the Java control panel. Some have had success with that.

Jonathan

The files are on two servers without a shared disk space so cp will not work. Rsync might work, but the solution I found is to tar the .sage directory, which preserves the symlinks. Then I copied the .tar file to the new server. Then I untarred the file on the new server.

#on old server:
        tar -c .sage -f .sage.tar
#copy to the new server (I used sftp).
#on new server in the root of the user where sage will run:
         tar -xf .sage.tar

Thanks, Jonathan

Does anybody have a script to migrate a bunch of notebook users to a new sage notebook server...I need to replace my server hardware. I've installed Sage 5.5 on the new hardware and thought I would just move the .sage directory from my old server, but have had no luck with that. There seem to be path issues. The new server does not expect to find the user files already in __store__.

I would like to maintain passwords as well. Thus I think I need the user.pickle, but copying this also causes errors.

The server I am trying to migrate from was running 5.1, but with the Flask notebook.

I haven't yet tried the process of building all the intermediate versions and stepping through them. I also think I may have the same problem, as I am unwilling to try it in place on the server that is still working.