zope as staging server
Hi, First of all, Zope is fantastic. However, in order to adapt it for my immediate task, I need to: 1) Make a prettier, easier interface for my userland (and for the suits, who love pretty graf-x) 2) Use Zope on the staging server only, and add a method to publish objects via arbitrary means (flat HTML, ftp, scp, rsync, whatever) I'm pretty sure #1 is a fairly simple matter of designing my own pages that call the various zope management methods. And #2 seems doable, but I'm not sure enough of the internal architecture of Zope to do this (nor have I programmed in Python before, tho it looks to be fairly obvious 00 stuff). Should I write an external method for this? I suppose the strategy would be to add properties to my Zope objects to hold info regarding the destination of the flat HTML, and then write a method to support them. Finally, has anyone done this already? JT
"Thaxter, Jason M." wrote:
Hi,
First of all, Zope is fantastic. However, in order to adapt it for my immediate task, I need to:
1) Make a prettier, easier interface for my userland (and for the suits, who love pretty graf-x) 2) Use Zope on the staging server only, and add a method to publish objects via arbitrary means (flat HTML, ftp, scp, rsync, whatever)
I'm pretty sure #1 is a fairly simple matter of designing my own pages that call the various zope management methods. And #2 seems doable, but I'm not sure enough of the internal architecture of Zope to do this (nor have I programmed in Python before, tho it looks to be fairly obvious 00 stuff).
Should I write an external method for this? I suppose the strategy would be to add properties to my Zope objects to hold info regarding the destination of the flat HTML, and then write a method to support them.
Why not just design your pages without infinite recursion and then just wget them for publishing ? -------------- Hannu
On Mon, 2 Aug 1999, Hannu Krosing wrote:
"Thaxter, Jason M." wrote:
Hi,
First of all, Zope is fantastic. However, in order to adapt it for my immediate task, I need to:
1) Make a prettier, easier interface for my userland (and for the suits, who love pretty graf-x) 2) Use Zope on the staging server only, and add a method to publish objects via arbitrary means (flat HTML, ftp, scp, rsync, whatever)
I'm pretty sure #1 is a fairly simple matter of designing my own pages that call the various zope management methods. And #2 seems doable, but I'm not sure enough of the internal architecture of Zope to do this (nor have I programmed in Python before, tho it looks to be fairly obvious 00 stuff).
Should I write an external method for this? I suppose the strategy would be to add properties to my Zope objects to hold info regarding the destination of the flat HTML, and then write a method to support them.
Why not just design your pages without infinite recursion and then just wget them for publishing ? And don't forget to use ids with an extension representing the right type. So use index.html, test.gif and test.jpg :)
Andreas -- Andreas Kostyrka | andreas@mtg.co.at phone: +43/1/7070750 | phone: +43/676/4091256 MTG Handelsges.m.b.H. | fax: +43/1/7065299 Raiffeisenstr. 16/9 | 2320 Zwoelfaxing AUSTRIA
participants (3)
-
Andreas Kostyrka -
Hannu Krosing -
Thaxter, Jason M.