gitstat-devel

[Gitstat-devel] New installation and configuration pages

[Paul V. <pau...@gm...>]

Hi,

Soon (I promise) I will commit the new installation page and the changed admin page.

This makes it possible to have a more-or-less graphical installation procedure. 
Next to that you should be able to create and change a configuration file from 
within the admin page.

The admin page will write out a new configuration file in gstat_rw/config/ and 
also create a template perlconfig.pl file. This file can then be copied and used 
in the gstat_pl part.

This is all nice for people that install from scratch. I'm currently struggling 
with how to approach this for people who upgrade. Any advise?

The old config.php file will be gone. We can of course ask the upgrader to copy 
the config.php file to:

1. gstat_rw/config/dbconfig.php
AND
2. gstat_rw/config/gitstatconfig.php

That should do the trick. As long as the account for the webserver has full 
access to those files (and that config directory). The config file will have to 
much information in them but that's not important anymore.

The step after this while installation/config stuff is to move the configuration 
piece to the database. That's post v0.5 however.

I don't need to tell you that we need a v0.5 soon but I don't want to rush this 
and have at least something halfway decent in place.

Cheers,

Paul.

Re: [Gitstat-devel] New installation and configuration pages

[Lee j. <jun...@gm...>]

Hi,

First of all, Thanks for your contribution.
Actually, I couldn't focus on gitstat these days, sorry for that.

I don't know the way of using dbconfig.php and gitstatconfig.php.
So, I couldn't tell about that well, but if it is needed to separate config.
php, your idea could be good solution.

With some perl code it could be separated easily. But it doesn't care a
whoop.

I'm waiting for new installation page. Someone said that gitstat is too
complex to install and use. If it is done, gitstat could be used by more
people.

Thanks,

 -----Original Message-----
From: git...@li... [mailto:gitstat-devel-
bo...@li...] On Behalf Of Paul Vriens
Sent: Wednesday, April 02, 2008 3:52 PM
To: git...@li...
Subject: [Gitstat-devel] New installation and configuration pages

Hi,

Soon (I promise) I will commit the new installation page and the changed
admin page.

This makes it possible to have a more-or-less graphical installation
procedure. 
Next to that you should be able to create and change a configuration file
from 
within the admin page.

The admin page will write out a new configuration file in gstat_rw/config/
and 
also create a template perlconfig.pl file. This file can then be copied and
used 
in the gstat_pl part.

This is all nice for people that install from scratch. I'm currently
struggling 
with how to approach this for people who upgrade. Any advise?

The old config.php file will be gone. We can of course ask the upgrader to
copy 
the config.php file to:

1. gstat_rw/config/dbconfig.php
AND
2. gstat_rw/config/gitstatconfig.php

That should do the trick. As long as the account for the webserver has full 
access to those files (and that config directory). The config file will
have to 
much information in them but that's not important anymore.

The step after this while installation/config stuff is to move the
configuration 
piece to the database. That's post v0.5 however.

I don't need to tell you that we need a v0.5 soon but I don't want to rush
this 
and have at least something halfway decent in place.

Cheers,

Paul.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Gitstat-devel mailing list
Git...@li...
https://lists.sourceforge.net/lists/listinfo/gitstat-devel

Re: [Gitstat-devel] New installation and configuration pages

[Paul V. <pau...@gm...>]

Lee jungseung wrote:
> Hi,
> 
> First of all, Thanks for your contribution.
> Actually, I couldn't focus on gitstat these days, sorry for that.
> 
> I don't know the way of using dbconfig.php and gitstatconfig.php.
> So, I couldn't tell about that well, but if it is needed to separate config.
> php, your idea could be good solution.

The idea behind this is that:

dbconfig.php holds the database configuration stuff (like GSTAT['ID'])
gitstatconfig.php holds all other configuration paramaters.

For people who are updating they can just copy their config.php to these new 
files. The functions in lib.php will make sure only the relevant stuff is extracted.

The dbconfig.php is always needed somewhere on the disk whereas the other stuff 
can reside anywhere we want.

gitstatconfig.php will be removed in the future and those parameters will reside 
in a/the database.

> 
> With some perl code it could be separated easily. But it doesn't care a
> whoop.

I actually thought about changing config.pl to do that but decided generating it 
from the admin page was so much easier. Especially as this will be moved partly 
to the database I didn't feel like touching config.pl.

This does however mean that the dbconfig.php has to change into a different kind 
of file/format so it can be read easily by both php and perl without too much 
hassle.

> 
> I'm waiting for new installation page. Someone said that gitstat is too
> complex to install and use. If it is done, gitstat could be used by more
> people.

I totally agree. I didn't know it would take this much effort though :-)
I will stop beautifying the installation and admin page, that's something we can 
do afterwards.

Cheers,

Paul.