I am facing a similar problem, and I am not sure how to handle it. It
would be nice to be able to create/destroy accounts for a notebook on
the command line. Eventually I would like to provide sage servers for
hundreds of students, and it has to be easier to administrate than it
is currently.
This semester I will be dealing with about 18 students, and I can
muddle through OK. This experience will probably generate a few
administrative feature requests from me.
-M. Hampton
On Jan 14, 9:10 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Jan 14, 2008 1:42 AM, bill purvis <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > On Monday 14 January 2008, William Stein wrote:
> > > On 1/13/08, bill.p <[EMAIL PROTECTED]> wrote:
> > > ...
> > > Just out of curiosity, for your purposes would it be OK for you to
> > > just make the accounts manually through the notebook interface?
> > > I.e., just do
> > > sage: notebook(accounts=True)
> > > then click the "Create a new account" button, make each account,
> > > and that's it. Or do you really have to automatically script making
> > > the new accounts? I ask, because I don't think anybody has really
> > > actually ever done the latter, and it's actually not something we
> > > have documented or really support doing. However, creating accounts
> > > through the notebook interface (i.e., via a web browser) is well
> > > supported.
>
> > > -- William
>
> > I wasn't aware of that method! I was thinking in terms of a system
> > administrator who wanted to keep control over who could login, though
> > in this case it's only accessible to me!
>
> > I think I've figured it out and managed to come up with a method of
> > getting it to work: I log in as admin, do the above command sequence
> > then follow up with:
>
> > nb.save('.....')
>
> > then log out.
>
> If you just use the command line you'll be in much better shape. The problem
> with doing any of the above via the notebook itself is that the notebook
> should overwrite any changes you make, since it writes out nb.sobj every so
> often (in particular, on exit).
>
> > Then: make a copy of nb.sobj because closing down the notebook will
> > rewrite it overwriting the changes I had made, close down the notebook,
> > then replace nb.sobj with the saved copy. I can then login as bill. :-)
>
> > I guess what needs to be done is to have some way to access the same copy
> > of nb.sobj that the login process is using.
>
> Don't start the notebook at all, and use the command line for everything.
> Once you've modified and save nb.sobj, then use the notebook.
>
>
>
> > I don't understand enough
> > about how it all works to know if this is possible? I presume that when
> > the notebook() call is made, the file is read in and that data structure
> > gets updated when the 'Create a new user' button is clicked, then it
> > gets written back when the notebook closes down.
>
> > Is this something worthwhile pursuing? I'll have a dig around and see
> > what I can figure out....
>
> > Bill
> > --
> > +---------------------------------------+
> > | Bill Purvis, Amateur Mathematician |
> > | email: [EMAIL PROTECTED] |
> > | http://bil.members.beeb.net |
> > +---------------------------------------+
>
> --
> William Stein
> Associate Professor of Mathematics
> University of Washingtonhttp://wstein.org
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
