unix_installer

  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
committing final changes for 2.2 unix upgrader - forgot to commit them earlier

  1. … 131 more files in changeset.
Fix a missing directory in lams-learning.war in the compress wars task

  1. … 1 more file in changeset.
committing sql dump for 2.2

    • binary
    ./installer-package/install-lams.sh
    • -81
    • +246
    ./installer-package/database/dump.sql
Fixing some typos in the removeConfig.sql scripts

  1. … 1 more file in changeset.
LI-177 adding dimdim as hidden for 2.2 updater

LI-178 Adding turkish language for the installers

Issues raised by Ivan Martinez Ortiz on the lams community forum fixed:

http://lamscommunity.org/dotlrn/clubs/technicalcommunity/forums/message-view?message_id=696448

    • -1
    • +1
    ./patch-package/ant-scripts/update_db.xml
making sure run.sh is executable

    • binary
    ./installer-package/install-lams.sh
Making sure dimdim tool is set to hidden for 2.2 install

  1. … 1 more file in changeset.
change of heart to include spreadsheet tool as not hidden for 2.2

  1. … 1 more file in changeset.
Making sure that the blob collumn in the lams_qtz tables do not create a risk of data corruptin in the lams dump

  1. … 2 more files in changeset.
Fixing run.conf to have the correct java memory settings

Fixing removeConfigs.sql to make sure it removes all lams_qtz trigger rows taht may have been created

LI-176 Ensuring run.conf has the correct java memory requirements if the user chooses to install without the wrapper

    • binary
    ./installer-package/install-lams.sh
    • -0
    • +50
    ./installer-package/conf/run.conf
LI-169 Adding new jars to default/lib for unix installers

    • binary
    ./installer-package/install-lams.sh
LI-167 check if mysql test works on a non-default mysql port

updated backup.java to use the mysql host and port in the mysqldump command so it will work for a non-default mysql port

    • binary
    ./upgrader-package/bin/backup.class
LI-169 - new jars to add to default/lib

LI-167 check if mysql test works on a non-default mysql port

adding not about ldap config changes to updaters

  1. … 1 more file in changeset.
updating the server versions

Fixing 2.2 unix updater to update from 2.1 and 2.1.1 LAMS versions

LI-164 - Adding a comment in the readme informing the sysadmin that they will need to re-install the flv player if they want it to work with 2.2

Adding a command to the update script for 2.2 to ensure that the spreadsheet tool is left as disabled for the 2.2 update

LI-161 - Fixing so a custom DEFAULT_DIR does not break the tool deployer

LI-167 Check if mysql works for a non-default port

updater is now changed to not prompt user for mysql port, it is retrieved either from lams.properties or the stored lams.properties instead

    • binary
    ./upgrader-package/bin/copyllid.class
New database dump for 2.2

    • -262
    • +1613
    ./installer-package/database/dump.sql
LI-172 uddating applicaion.xml and context.xml to comply with 2,2 requirements

    • -2
    • +19
    ./installer-package/conf/j2ee/application.xml
LI-161 Making sure that all the directory variables point to the correct location, if one is edited, it is the user responsibility to make sure it still works

LI-168 making sure only the required files are included in the package

Updating the version numbers

    • binary
    ./installer-package/install-lams.sh
Adding an extra script for removing config items like the gmap key, that way they dont have to be done every time you need to dump a new version of the database

The limitation of this is that you still have to delete the unused users and start the sample lessons

    • -0
    • +14
    ./installer-package/sql-scripts/removeConfigs.sql
Un-commenting the script that updates the lams versions. This was going to be handled by autopatch, but that would mean that the server version numbers would not be updated for a normal build

LI-167 Check if mysql test works for a non-default mysql port

the problem here was not with jdbc but instead with shell, the SQL_URL's '&' character was getting munged by shell, so escaping it here did the trick