Hi!
> Hmm ... now to write the web interface ;-)
Not before we have a decent templating system ;-)
bye, Georg
On Mon, Dec 09, 2002 at 12:52:17PM +0100, Georg Bauer wrote:
> I just checked in the ability to add aliases to user records in the
> database and to automatically generate corresponding rewrite rules.
> Added are some commands to pycsadm as follows:
>
[...]
>
> This is in preparation for web-based configuration interfaces and maybe
> someday user-defined aliasing. Most of the actual code is in
> pycs_settings.py. pycsAdmin.py and pycs.py just use the code that's in
> pycs_settings.py. A little change was needed for pycs_rewrite_handler.py
> to enable reloading the rewrite rules after changing something in the
> database without the need to reload the whole config.
Great job!
Hmm ... now to write the web interface ;-)
Cheers,
Phil
Hi!
Just to answer a question that might come up: why not drop the pycs.conf
and rewrite.conf based aliases? Simple: the in-database aliases can only
work with a standard name scheme, either http://server.doma.in/alias or
http://alias.server.doma.in - but if you for example want to set up
user-owned domains, you have to add pycs.conf based aliases, as those
can't be deduced from the database (and since user-owned domains will
always require several actions by admins, it's of no use to pull them
into the database, too). So with pycs.conf and rewrite.conf you can set
up for example http://xgwskba.de/ to point to
http://muensterland.org/users/0000004, with just one entry in pycs.conf
and one (or two) rewrite rules in rewrite.conf.
bye, Georg
> I just saw that somebody (Phil I assume) added some more attributes to
> the community stuff in xmlStorageSystem. But shouldn't the
> "discussionGroupUrl" and the "mailListUrl" point to pycs related groups
> and lists? They now point to Radio Userland. Hmm.
>
> And could we make the community name a configuration option - or must
> that be the product name of the community server? I don't know how those
> attributes are used outside, that's why I ask.
Ah, yes. I put those in as placeholders after finding out that Radio was
failing miserably when pinging the community server when the 'community'
struct was set in the xmlStorageSystem.ping() response but various
attributes ('title', etc) weren't.
The community name shouldn't be 'Python Community Server', and it would be
fine to point the discussion and mailing list URLs over here. Feel free to
change them (put them in pycs.conf).
Cheers,
Phil :)
Hi!
I just checked in the ability to add aliases to user records in the
database and to automatically generate corresponding rewrite rules.
Added are some commands to pycsadm as follows:
pycsadm.py alias simple 0000004 xgwskba
- this sets a new alias in the http://muensterland.org/xgwskba format
pycsadm.py alias manila 0000004 xgwskba
- this sets a new alias in the http://xgwskba.muensterland.org format
The corresponding rewrite rules (both the redirect when entering the old
usernumber format and the rewrite from the alias to the usernumber
format) are generated automatically. What is not generated is the manila
style rewrite, as that is only one rule in the rewrite.conf (the other
two rules are generated for every alias).
pycsadm.py alias del 0000004
- this deletes the alias and the corresponding rewrite rules
pycsadm.py list aliases
- this lists all in-database aliases (not aliases from the pycs.conf!)
pycsadm.py list rewrites
- this lists all defined rewrite rules (only the descriptional string,
both in-database and pycs.conf!)
Both pycs.conf/rewrite.conf and in-database aliases continue to work
together - actually my muensterland.org currently has two .conf-aliases
and one in-database alias. So if you don't use the feature, as always,
nothing changes for you (hopefully).
This is in preparation for web-based configuration interfaces and maybe
someday user-defined aliasing. Most of the actual code is in
pycs_settings.py. pycsAdmin.py and pycs.py just use the code that's in
pycs_settings.py. A little change was needed for pycs_rewrite_handler.py
to enable reloading the rewrite rules after changing something in the
database without the need to reload the whole config.
bye, Georg
Hi!
Another question: the flHasSearch and urlSearch currently are set to
false and ''. What would be needed to implement it - I think a module in
system, setting up the URL, but what should be searched? All users, or
only the user where the search is called? An "all users search" can be
done with google, with a link restriction to the domain of the community
server. So maybe we actually don't need to implement anything but just
point over to google?
bye, Georg
Hi!
I just saw that somebody (Phil I assume) added some more attributes to
the community stuff in xmlStorageSystem. But shouldn't the
"discussionGroupUrl" and the "mailListUrl" point to pycs related groups
and lists? They now point to Radio Userland. Hmm.
And could we make the community name a configuration option - or must
that be the product name of the community server? I don't know how those
attributes are used outside, that's why I ask.
bye, Georg
