Emiliano wrote:
>
> > You need to have apache and mysql running locally. The question is, what
> > are you going to do with the site. Are you going to transfer it later on
> > to a midgard-enabled server or are you going to export the html
> > statically? Both can be done, but the latter is probably not very
> > useful.
>
> It can be. I used to use Midgard to develop a site on a intranet server
> which was wgetted & rsynced to an external (non-midgard) server.
Of course, technically it can be done without much manual maintainance
work (using mirroring tools and cronjobs, as you described).
I was just refering to the fact that everything will be static - frozen,
if you like. No (php)-POST or GET, let alone online content editing
since all the php is replaced by its html output. For this kind of work
(*compiling* a web site from content and macro code) there are a number
of tools out which are less complex than midgard. I used to use gtml
which is probably the most archaic one of these.
Frank
--
Dr Frank Boehme | Email: [EMAIL PROTECTED]
National University of Ireland, Cork | phone: +353-21-903163
Dept of Computer Science | fax: +353-21-903113
Cork, Ireland |
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
