You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+51-13Lines changed: 51 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,16 +9,54 @@ includes a Vagrant VM on which these tools can be developed and tested.
9
9
This repo also contains the mapping of hooks to specific project id's for the
10
10
production and staging instances of REDCap at the CTSI.
11
11
12
-
13
12
## Requirements
14
13
15
14
A user of these tools will need to download and provide their own REDCap zip file,
16
15
downloaded from Vanderbilt. This REDCap .zip should be placed in the root folder.
17
16
It should not be renamed.
18
17
19
-
This VM requires that Vagrant, VirtualBox, the vagrant-hostsupdater plugin and the vagrant-env plugin be installed on the host system.
18
+
This VM requires that Vagrant, VirtualBox, the vagrant-hostsupdater plugin and
19
+
the vagrant-env plugin be installed on the host system.
20
+
21
+
22
+
### Install Vagrant and Virtual Box
23
+
24
+
On a Linux machine run these commands in a shell:
25
+
26
+
sudo apt-get install vagrant
27
+
sudo apt-get install virtualbox
28
+
29
+
On a Mac OSX machine:
30
+
31
+
- Download and install vagrant from <https://www.vagrantup.com/downloads.html>
32
+
- Download and install the latest virtual box from <http://download.virtualbox.org/virtualbox/>
33
+
34
+
On Mac OSX users using [Homebrew](http://brew.sh/) can install these packages
35
+
using the _brew_ command. Run these commands at a shell:
36
+
37
+
brew install virtualbox
38
+
brew install vagrant
39
+
20
40
21
-
See [Creating the Test VM With Vagrant](docs/creating_the_test_vm_with_vagrant.rst) for details on how to meet those requirements.
41
+
### Install Vagrant plugins
42
+
43
+
Vagrant will need a few plugins for this VM. On any platform, run these commands in a shell:
44
+
45
+
vagrant plugin install vagrant-hostsupdater
46
+
vagrant plugin install vagrant-env
47
+
48
+
Mac OSX users might enjoy the functionality of the vagrant-triggers plugin. CTS-IT used it to open the Chrome browser to the just -deployed REDCap instance. Run this command at a shell to install it.
49
+
50
+
vagrant plugin install vagrant-triggers
51
+
52
+
For more details about Vagrant software you can go to [why-vagrant](https://docs.vagrantup.com/v2/why-vagrant/) page.
53
+
54
+
55
+
### Get your REDCap zip file
56
+
57
+
You must provide a copy of the REDCap software from http ://project-redcap.org/. Save the .zip file with its default name to the root of this repository. This ensures the provisioning script [bootstrap.sh](bootstrap.sh) script can extract the files to the virtual machine path "**/var/www/redcap**".
58
+
59
+
If you put multiple redcap\*.zip files in the vagrant folder, the provisioning script will use the one with the highest version number.
22
60
23
61
24
62
## Configure the Development Environment
@@ -29,6 +67,7 @@ use. Minimally, you will need to set _smtp\_smarthost_ the dns name of a mail
29
67
server your development host can use to deliver mail. This will allow you to
30
68
better test features that send email.
31
69
70
+
32
71
## Using the Development Environment
33
72
34
73
With the above requirements and configuration completed, start the VM with the command
@@ -38,33 +77,32 @@ With the above requirements and configuration completed, start the VM with the c
38
77
After about two minutes, the VM should be accessible at [http://redcap.dev/redcap/](http://redcap.dev/redcap/) and at [https://redcap.dev/redcap/](https://redcap.dev/redcap/) (or whatever URL _URL\_OF\_DEPLOYED\_APP_ is set to in _.env_)
39
78
40
79
41
-
## Hook and Plugin deployment
80
+
## Hook and Plugin Deployment
42
81
43
82
CTSI REDCap Hooks and Plugins are deployed using the script
44
83
deploy_extensions.sh in this repo. This repo also contains the data files
45
84
need to configure hook deployment for the CTSI REDCap instances. See [Hook
46
85
Deployment ](README-hooks.md) for usage instructions and details.
47
86
48
87
49
-
## REDCap upgrade
88
+
## REDCap Upgrade
50
89
51
-
Upgrade instructions currently live in a Wiki article found at
52
-
[CTS-IT Wiki Article on REDCap Upgrades](https://ctsit-forge.ctsi.ufl.edu/projects/redcap/wiki/REDCap_Upgrade_Instructions)
90
+
At the moment, CTS-IT does not have a fully scripted upgrade or procedures
91
+
that can be be shared publicly. The upgrade procedures used live in a private
92
+
Wiki article found at [CTS-IT Wiki Article on REDCap Upgrades](https://ctsit-
0 commit comments