[basedb-cvs] basedb README,1.21,1.22

[<tr...@us...>]

Update of /cvsroot/basedb/basedb
In directory sc8-pr-cvs1:/tmp/cvs-serv25237

Modified Files:
	README 
Log Message:
Updated ftpd stuff, migration stuff

Index: README
===================================================================
RCS file: /cvsroot/basedb/basedb/README,v
retrieving revision 1.21
retrieving revision 1.22
diff -C2 -d -r1.21 -r1.22
*** README	12 Feb 2003 17:57:02 -0000	1.21
--- README	13 Feb 2003 12:22:47 -0000	1.22
***************
*** 265,283 ****
  
  Included with BASE is an FTP server which can be used to upload/download
! file to/from BASE. In the future it'll also handle downloads of other types.
! If you want to use it, here's how: When you compiled the things in
! exec/source, two programs called spawner and baseftpd were created and
! copied to exec/baseftpd. baseftpd needs to be started by inetd, but in the
! case that you don't have access to inetd.conf (my situation on the BASE
! development box), spawner can be used instead, e.g.
!  nohup ./spawner 2121 ./baseftpd &
! to listen for connections on port 2121. Using inetd (the normal solution),
[...72 lines suppressed...]
*** 310,313 ****
    This will - if all goes well - copy data from the old databases to the
    new, and at the same time modify the data directory as needed.
! Start BASE using the script exec/restart.php
  
--- 315,328 ----
    This will - if all goes well - copy data from the old databases to the
    new, and at the same time modify the data directory as needed.
! Start BASE using the script bin/startBase.php as described above.
! 
! If you have BASE 1.2.0RC1 installed, upgrading to RC2 will be relatively
! painless. You can use the old data directory without any changes, but the
! rest of the old installation needs to be replaced. There have been a few
! changes to the things required in config.inc.php, so you should copy the
! new example_config.inc.php and modify with things from your old config.
! Finally, there have been three changes to the database schema. Two of
! these can be considered bug fixes, and the third was just something I'd
! forgotten to add. The file sql/upgrade_rc1_to_rc2.sql contains the SQL
! statements that need to be run to get the schema up to date.