Skip to content

Releases: ctsit/redcap_deployment

REDCap Deployment

13 Dec 02:52
Compare
Choose a tag to compare

REDCap Deployment provides tools for scripted deployments and upgrades of REDCap instances and the extensions installed within them. The project provides a toolset to build packages rapidly and consistently across REDCap version numbers and deploy those packages to new and existing REDCap instances.

Releases 1.3.0 - 3.2.1 provide these changes:

  • Add upgrade_apply_incremental_db_changes_only task (@pbchase)
  • Add PHP 7.4-to-8.1 upgrade instructions (@pbchase)
  • Add PHP Configuration section to README (@pbchase)
  • Add 'Development tools' documentation (@pbchase)
  • Add database dump commands for root and vagrant users (@pbchase)
  • Update post deployment tests (@pbchase)
  • Exclude MacOSX's ._* files from the packaged REDCap code (@pbchase)
  • Improve docs for installing custom PHP packages (@pbchase)
  • Fix BSD tar bug in package.py (@pbchase)
  • Add commits to /etc during the php upgrade steps (@pbchase)
  • Install PHP 7.4, all PHP modules, and composer in README (@pbchase)
  • Add code fences, update header depth (@ChemiKyle)
  • Suppress warning during mysqldump (@pbchase)
  • Set modern permissions on the admin user (@pbchase)
  • Update example.env.txt (@mbentz-uf)
  • Update CONFIG_VM_BOX to generic/debian (@mbentz-uf)
  • Add group write permission to module directory (@mbentz-uf)
  • force composer version to 1.x in all scripts where composer is installed needed due to incompatibility with wikimedia/composer-merge-plugin
    deploy/composer/deploy.sh affects fab instance package (@ChemiKyle)
  • update vagrant mysql, 5.6 -> 5.7 required to use redcap_v10.3.0 (@ChemiKyle)
  • update gpg servers for mysql (@ChemiKyle)
  • recreate the definition of constants from upgrade.php in generate_upgrade_sql_from_php.php (@ChemiKyle)
  • use default browser when auto-opening site (@ChemiKyle)
  • Add rm_ssh_key task to server_setup.py (@pbchase)
  • Make patch deploy scripts executable in package.py (@pbchase)
  • relocate and rename vt (@ChemiKyle)
  • Removed README references to pycurl after confirming it is not needed (@ChemiKyle)
  • pycurl replaced with urllib, BytesIO no longer needed (@ChemiKyle)
  • Update for vboxsf fileshare (@ChemiKyle)
  • Change sync type to nsf as nsf causes other issues. (@marlycormar)
  • Use nfs to keep shared folder syncronized. (@marlycormar)
  • Update links, wrap commands in blocks, additional osx pycurl help (@ChemiKyle)
  • Use Vagrant's built-in triggers functionality (@pbchase)
  • Update vm to php7.2. (@marlycormar)
  • Upgrade to Python3(@pbchase)
  • Provide support for using REDCap's non-upgrade packages during upgrades (@pbchase)
  • Add PHP Zip extension and SOAP package in Dev VM. (@tbembersimeao)
  • Add .gitattributes file to manage line ending configuration. (@mattkoch614)
  • Add a cron task to deploy.py (@pbchase)
  • Add support for External Modules. (@tbembersimeao)

1.2.0 - Add deployments, tests, test configurations, PRMIS fixes, and Messenger configuration

20 Sep 15:15
Compare
Choose a tag to compare

This release adds deployment scripts for 3 new REDCap extensions and two tests related to SendIt. It provides SQL scripts to simplify testing with table-based authentication, fix issues wit bad PRMIS credentials, and disable REDCap Messenger. It provides enhanced SSL security for the local apache instance. The release also fixes bugs related permission errors during deployment and PHP5 installation.

1.0.0 - Fabric-based packaging and deployment tools

19 May 21:18
Compare
Choose a tag to compare

This release replaces BASH-based REDCap deployment with a Python Fabric-based toolset that allows scripted building and deployment of packages containing REDCap code and the extensions a site wants to layer upon it. The packaging scripts support hooks, plugins, language modules, and modifications to REDCap core. Packages are built rapidly and consistently across any REDCap version. These packages are used to provision new REDCap instances or upgrade existing ones.

Scripted upgrade processes integrate new code with existing code, manage all required database updates, and run post-deployment tests to verify the deployment. This toolset reduces variability between development, testing, and production environments. This in turn reduces error rates and the costs of upgrading REDCap instances.

[0.6.0] - 2016-08-01

01 Aug 19:00
Compare
Choose a tag to compare

[0.6.0] - 2016-08-01

What changed?

  • Merge Requirements section from docs/creating_the_test_vm_with_vagrant.rst into README and update text of README (Philip Chase)

What was added?

  • Add condensed_pdf_report plugin (Philip Chase)

Release [0.5.0] - 2016-06-14

15 Jul 18:57
Compare
Choose a tag to compare

What changed?

  • Refactor dev VM and its related deployment scripts to use the vagrant-env plugin, Debian Jessie, and
    MySQL Community Server (Philip Chase)
  • Fix formatting errors in 'Creating the Test VM With Vagrant' and embellish content (Philip Chase)
  • Use our apache ssl configuration (Philip Chase)
  • Check for box file updates at 'vagrant up' (Philip Chase)
  • Reconfigure how the autonotify plugin deployment integrates with apache (Philip Chase)

First public release

25 Apr 19:53
Compare
Choose a tag to compare

This is the first public release of the internal REDCap Deployment scripts the UF CTSI is using to test and deploy REDCap Hooks and Plugins in development, staging, and production environments.