GnuDIP 2.1.2


Upgrade from 2.1.1 to 2.1.2
 gdips.pl changes. Copy the new gdips.pl over your old one and restart it.

 OR run ./install -upgrade and it will ask for your config again and copy all new files
  to their new places, without messing up your old database setup. Eventually this
  method will read your old config and just do the upgrade automatically.


Upgrading from 2.1.0 to 2.1.1
 Simply copy the gnudip2.cgi over your old one.


Upgrading from 2.0.6 to 2.1.0
 Unfortunatly beacuse the way data is stored in the database all users are going to have to re signup. This may seem like a hassle, but it is for the best and hopfully this will not have to be done again. The best thing to do is to completely drop the 'gnudip2' database and then create it back then run 'mysql < gnudip2.db'. This should rebuild all tables to the new format. You will need to replace the gdips.pl and gdipc.pl scripts over their old ones. Also move gnudip-lib.pl to where gnudip-conf.pl is at in your perl library directory (usaully /usr/lib/perl5). gdip-named.pl and gnudip.cron have ben merged into gdips.pl so you will no longer need them. Remove the gnudip cron entry from your system if you were using that. I hope I did not leave anything out, but if you have any problems or know of anything I forgot please let me know.


Upgrading from 2.0.5 to 2.0.6

 add the tmpdir = /tmp directive to your /etc/gnudip.conf (See gnudip.conf in this distribution for a sample)
 Copy the gdip-named.pl on top of your old script



Upgrading to 2.0.6 from lower than 2.0.5

Configuration is now stored in /etc/gnudip.conf

gnudipuser is the user you have current scripts using to connect to the database
gnudippassword is the password you have current scripts using to connect to the database
runasuser is the user you are su'ing into to run the gdips.pl
runasgroup is the group you want to have the daemon run under
pidfile is the path to the file that contains the pid of the gdips.pl process
gnudipserver is the hostname the database resides on

A template can be found in the gnudip.conf included in this distribution

*NOTE* Be sure to set owner on /etc/gnudip.conf to root and group to your web servers group. Then chmod to 640 to prevent users from getting direct database access to your gnudip2 database


No database layout has changed, so all that is needed is to replace the following scripts

gdips.pl
gdip-named.pl
gnudip2.cgi
S99gnudip

gnudip-conf.pl needs to be placed into your perl5 library directory, usually /usr/lib/perl5

Change #PREFIX# in S99gnudip to the prefix you used on the original install of GnuDIP

To allow for the new custom header on the login screen the following command shoulw be executed on the gnudip2 database:
  insert into globalprefs values ("","HEADER_FILE","");




If you are going to reinstall and are not worried about loosing users, make sure to do mysqladmin drop gnudip2 or equivallent for your database