[pmwiki-users] Re: How to 'automatically' keep a deployed PmWiki install up to date?

[Waylan Limberg]

On 9/25/05, Crisp, Steve [UK] <SCRISP at ngms.eu.com> wrote:
>
>
> To date we've been looking at source code configuration systems to help us
> maintain our system installations.  This approach effectively remembers what
> you have checked out allowing you to 'update' your installations.
>
> What about the reverse perspective, how can get we request from the PmWiki
> core a list of all installed plug-ins - perhaps a plug-in registration
> mechanism?
>
> A single Wiki page could be configured to report the system configuration.
>
> Any ideas on how this can be achieved over and above {$Version} for PmWiki
> core?

I like this idea myself. I suppose there are a few different ways this
could be done, but you'd need the authors of each plugin/recipe to
follow convention in their code for it to show up. They would need to
follow some pre-defined comment formatting on the first few lines or
define a few variables. I'd think the variables would be easiest.
Something like:

$recipe['name'] = "SomeName";
$recipe['version'] = "0.0.1";
$recipe['description'] = "A short description of what the script does.";

Then the code to iterate through the array and list each of the
recipes would be pretty straightforward.

If the data was in the comments (like some other projects require)
then a script would have to scan all the files in the cookbook dir and
read the comments looking for the proper formatting. Of course, a
recipe can be in the cookbook, but if it's not included from
config.php, then its not enabled so you'd have to check for that. Then
you have recipes only enabled in some farms/groups/pages but not all
(via groupname.php for example). That throws another wrench in the
works. Guess that's why I like the array above. But then, if the page
displaying the data is in a different group which was not included on
this page, how do you deal with that?

Like I said, the authors of the various recipes would need to comply
with the convention in their code, which may or may not happen. Of
course, as it currently stands, to my knowledge, none of the recipes
have anything of the sort, although I suppose some are better
documented in the comments than others. It would be interesting to see
how others would do this.

> -Steve.
>
>
>  ________________________________
>  From: pmwiki-users-bounces at pmichaud.com on behalf of
> chr at home.se
> Sent: Sun 25/09/2005 17:49
> To: pmwiki-users at pmichaud.com
> Subject: [pmwiki-users] Re: How to 'automatically' keep a deployed PmWiki
> install up to date?
>
>
>
>
> On Mon, 26 Sep 2005, Robin wrote:
>
> > On Monday 26 September 2005 03:17, Crisp, Steve [UK] wrote:
> > > I still think a separate repository, let's call it a staging area might
> > > simplify things especially if the update mechanism needed nothing more
> > > than you already have to run PmWiki (php, web server, browser).  Unless
> > > there is a php CVS client class out there that can be reused!
> >
> > Might I recommend that if you do something like this, you look into
> > subversion. It's usable just the same as CVS (it was designed to be easy
> > to go from one to the other), but avoids many of the issues that you end
> > up unconsciously working around in CVS, leading to less repository
> > maintenance and more just using it.
>
> I agree... in fact, maybe Patrick should switch pmwiki to subversion as
> well? That's totally up to him of course, and pmwiki is so stable now that
> many of the reasons for using subversion probably doesn't apply in case.
> But it might be useful?
>
> /Christian
>
> --
> Christian Ridderström, +46-8-768 39 44
> http://www.md.kth.se/~chr
>
>
>
> _______________________________________________
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
> http://host.pmichaud.com/mailman/listinfo/pmwiki-users
>
> _______________________________________________
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
> http://host.pmichaud.com/mailman/listinfo/pmwiki-users
>
>
>


--
----
Waylan Limberg
waylan at gmail.com