Filesystem Directory View, etc.
Hi all, I'm trying to get some Webalizer stats accessible from a Zope instance. The problem is FSDV transforms any .html .htm .dtml document (it just rips the extension). I don't know why it does that, nor how I could tell FSDV not to do it, but it's a little rude since Webalizer builds many html pages that are linked together according to their full names (name+ext). So the navigation from imported Webalizer pages into FSDV is broken. Also note that while it's possible to tell Webalizer to produce various extension names for the files it builds, I don't see how to tell him NOT to produce any. Anyone has an idea how to proceed ? Thanks, Aurélien.
I'm trying to get some Webalizer stats accessible from a Zope instance.
The problem is FSDV transforms any .html .htm .dtml document (it just rips the extension). I don't know why it does that, nor how I could tell FSDV not to do it, but it's a little rude since Webalizer builds many html pages that are linked together according to their full names (name+ext). So the navigation from imported Webalizer pages into FSDV is broken.
Also note that while it's possible to tell Webalizer to produce various extension names for the files it builds, I don't see how to tell him NOT to produce any.
Anyone has an idea how to proceed ?
Put Apache in front of your Zope and create suitable rewrite rules to serve out your stats and Zope content side by side... jens
Le sam 04/10/2003 à 19:17, Jens Vagelpohl a écrit :
I'm trying to get some Webalizer stats accessible from a Zope instance.
The problem is FSDV transforms any .html .htm .dtml document (it just rips the extension). I don't know why it does that, nor how I could tell FSDV not to do it, but it's a little rude since Webalizer builds many html pages that are linked together according to their full names (name+ext). So the navigation from imported Webalizer pages into FSDV is broken.
Also note that while it's possible to tell Webalizer to produce various extension names for the files it builds, I don't see how to tell him NOT to produce any.
Anyone has an idea how to proceed ?
Put Apache in front of your Zope
That's how it works now...
and create suitable rewrite rules to serve out your stats and Zope content side by side...
Maybe I'll end up doing that, but I'm a bit frustrated with FSDV. Also I have no idea about how to create 'suitable' rewrite rules - that may take more time than I can allocate to this (digging thru the doc & guessing how to build those rules). Thanks, Aurélien.
On Sat, Oct 04, 2003 at 07:28:02PM +0200, Aurélien Campéas wrote:
and create suitable rewrite rules to serve out your stats and Zope content side by side...
Maybe I'll end up doing that, but I'm a bit frustrated with FSDV. Also I have no idea about how to create 'suitable' rewrite rules - that may take more time than I can allocate to this (digging thru the doc & guessing how to build those rules).
It's not that difficult (5-15 minutes of skimming through mod_rewrite docs and looking at the examples) and it's worth it. You can do wonderful things with rewrite rules. Marius Gedminas -- If the facts don't fit the theory, change the facts. -- Albert Einstein
On Sat, Oct 04, 2003 at 05:18:45PM +0200, Aur?lien Camp?as wrote:
Hi all,
I'm trying to get some Webalizer stats accessible from a Zope instance.
The problem is FSDV transforms any .html .htm .dtml document (it just rips the extension). I don't know why it does that, nor how I could tell FSDV not to do it, but it's a little rude since Webalizer builds many html pages that are linked together according to their full names (name+ext). So the navigation from imported Webalizer pages into FSDV is broken.
Also note that while it's possible to tell Webalizer to produce various extension names for the files it builds, I don't see how to tell him NOT to produce any.
Anyone has an idea how to proceed ?
I use Analog which I was easily able to configure to put its output into a file named index_html, which I server via LocalFS. Works fine. LocalFS would work ok for webalizer too - it doesn't strip extensions. Only problem is, LocalFS doesn't prevent edits TTW like FSDV does - but you can enforce that by setting permissions (either on the filesystem so the zope process ownere cannot write to that directory, or in zope by configuring permissions on the LocalFS instance). -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's GRATUITOUS KABUKI WARRIOR-TONGUE! (random hero from isometric.spaceninja.com)
I use Analog which I was easily able to configure to put its output into a file named index_html, which I server via LocalFS. Works fine. LocalFS would work ok for webalizer too - it doesn't strip extensions. Only problem is, LocalFS doesn't prevent edits TTW like FSDV does - but you can enforce that by setting permissions (either on the filesystem so the zope process ownere cannot write to that directory, or in zope by configuring permissions on the LocalFS instance).
I've tried to serve webalizer files through Zope myself at some point, but I didn't really see the point. I could not find a way to customize webalizer to create output that would really "fit seamlessly" into the look and feel laid down by my design in Zope. After that it just felt wasteful to serve those files through Zope for basically no gain, so I set it up in Apache. jens
Le sam 04/10/2003 à 19:46, Jens Vagelpohl a écrit :
I've tried to serve webalizer files through Zope myself at some point, but I didn't really see the point. I could not find a way to customize webalizer to create output that would really "fit seamlessly" into the look and feel laid down by my design in Zope. After that it just felt wasteful to serve those files through Zope for basically no gain, so I set it up in Apache.
I understand that (well I've thought about some hackish perl script that would cut the html output of webalizer, but it's not really worth the pain). But the graphics CAN be nicely (seamlesly) used within any Zope (or Plone) site. After all I don't really need all the nice crap Webalizer produces, juste the few graphs (that would likely make some impression on my customers :). It's just that FSDV is frustrating (as a tool). I'll have a look at LocalFS. Regards, Aurélien.
Le sam 04/10/2003 à 19:35, Paul Winkler a écrit :
I use Analog which I was easily able to configure to put its output into a file named index_html, which I server via LocalFS. Works fine. LocalFS would work ok for webalizer too - it doesn't strip extensions. Only problem is, LocalFS doesn't prevent edits TTW like FSDV does - but you can enforce that by setting permissions (either on the filesystem so the zope process ownere cannot write to that directory, or in zope by configuring permissions on the LocalFS instance).
You mean http://zope.org/Members/jfarr/Products/archive/LocalFS ? It has not been updated since early 2001. Is it still a viable Product ? I'll have a look anyway, thanks for this suggestion. Aurélien.
For local file system take a look at http://sourceforge.net/projects/localfs It's in wide use. On Sat, 4 Oct 2003, [ISO-8859-1] Aur�lien Camp�as wrote:
Le sam 04/10/2003 � 19:35, Paul Winkler a �crit :
I use Analog which I was easily able to configure to put its output into a file named index_html, which I server via LocalFS. Works fine. LocalFS would work ok for webalizer too - it doesn't strip extensions. Only problem is, LocalFS doesn't prevent edits TTW like FSDV does - but you can enforce that by setting permissions (either on the filesystem so the zope process ownere cannot write to that directory, or in zope by configuring permissions on the LocalFS instance).
You mean http://zope.org/Members/jfarr/Products/archive/LocalFS ?
It has not been updated since early 2001. Is it still a viable Product ?
I'll have a look anyway, thanks for this suggestion.
Aur�lien.
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Thanks to all the people that answered (and the other...). I'll stick with LocalFS. Aurélien.
The problem is FSDV transforms any .html .htm .dtml document (it just rips the extension). I don't know why it does that, nor how I could tell FSDV not to do it, but it's a little rude since Webalizer builds many html pages that are linked together according to their full names (name+ext). So the navigation from imported Webalizer pages into FSDV is broken.
FSDV is a "port" of the CMF's skins stuff to regular Zope. Most Zope objects don't have "filename extensions", but have a type instead, but filesystem objects are the other way round. Because the skins want to look like regular zope objects FSDV uses the extensions to determine type and then discards them. If you want to put an extension on a skinned object, you can put a double extension on the file, and only the first will be stripped off. If you want a full mapping of the filenames (for import of things that reference each other, for instance, and you don't want to fix that) you can use LocalFS instead. FSDV is more for using a self-developed skin from the FS than using existing content whole.
Also note that while it's possible to tell Webalizer to produce various extension names for the files it builds, I don't see how to tell him NOT to produce any.
As above, you could make it say name.html.html and it would work fine. --jcc -- "Code generators follow the 80/20 rule. They solve most of the problems, but not all of the problems. There are always features and edge cases that will need hand-coding. Even if code generation could build 100 percent of the application, there will still be an endless supply of boring meetings about feature design." (http://www.devx.com/java/editorial/15511)
participants (6)
-
Aurélien Campéas -
Dennis Allison -
J Cameron Cooper -
Jens Vagelpohl -
Marius Gedminas -
Paul Winkler