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: INSTALL.md
+24-8Lines changed: 24 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ cp .env.example .env
38
38
This command copies the `.env.example` into `.env`, creating the `.env` file in the process if it does not exist.
39
39
40
40
2. Open `.env` with a text editor (i.e. Notepad, VS Code, etc.) and make the necessary changes to the following variables:
41
-
-`APP_ENV`: If you are setting up a development environment, change this to `dev` and follow the steps in [Installing Composer Dependencies](#installing-composer-dependencies) without the `--no-dev` flag to obtain all of the development packages. Otherwise, leave it as `prod`.
41
+
-`APP_ENV`: If you are setting up a development environment, change this to `dev`. Otherwise, leave it as `prod`.
42
42
-`DATABASE_URL`: If you are hosting UDOIT on Docker or your local machine, leave it as it is. Otherwise, change it to your database URL.
43
43
-`BASE_URL`: If you are hosting UDOIT on Docker or your local machine, leave it as it is. Otherwise, change it to the URL of your instance of UDOIT.
44
44
-`WEBPACK_PUBLIC_PATH`: Uf you are hosting UDOIT on Docker or your local machine, leave it as it is. Otherwise, change it to match the `BASE_URL`in such a way that `/build` is located at the root of the `BASE_URL` (Example: If your `BASE_URL` is set to `http://127.0.0.1:8000`, your `WEBPACK_PUBLIC_PATH` should be `/build`).
@@ -51,20 +51,31 @@ This command copies the `.env.example` into `.env`, creating the `.env` file in
51
51
### Option 1: Docker
52
52
We provide a fast and simple way of setting up a local UDOIT instance through Docker.
53
53
54
-
1. Install [Docker Desktop](https://docs.docker.com/get-docker/). This will install Docker and Docker Compose on your system.
55
-
> Alternatively, you may install Docker and [Docker Compose](https://docs.docker.com/compose/install/) individually.
54
+
#### 1. Install [Docker Desktop](https://docs.docker.com/get-docker/). This will install Docker and Docker Compose on your system.
55
+
> Alternatively, you may install Docker and [Docker Compose](https://docs.docker.com/compose/install/) individually.
56
56
57
-
2. Build the Containers
57
+
#### 2. (Optional) Install the Necessary PHP Dependencies for Dev Environment
58
+
59
+
UDOIT uses Composer to install PHP dependencies. If your `APP_ENV` is set to `prod`, UDOIT will handle this for you. However, if it is set to `dev`, you may need some additional dependencies.
60
+
61
+
You can set them up by running the following command:
62
+
```
63
+
docker compose -f docker-compose.nginx.yml run composer composer install
64
+
```
65
+
66
+
#### 3. Build the Containers
58
67
59
68
```
60
69
make start
61
70
```
62
71
63
-
3. Once the containers are initialized, run the following command:
72
+
*Note: This may take a while to fully initiate. This is normal.*
73
+
#### 4. Set Up Database
74
+
75
+
The following command applies migrations necessary to set up the database to store all UDOIT data. Please make sure the containers have fully spun up before running this command.
64
76
```
65
77
make migrate
66
78
```
67
-
This applies migrations necessary to set up the database to store all UDOIT data.
68
79
69
80
Running this will give the following warning:
70
81
@@ -76,12 +87,14 @@ Type `yes` and proceed. The warning is expected and is a non issue.
76
87
77
88
UDOIT should be installed and running as Docker containers.
78
89
79
-
4. To stop the UDOIT containers, run the following command:
90
+
####To stop the UDOIT containers, run the following command:
80
91
```
81
92
make down
82
93
```
83
94
84
-
> Please be sure to review the `makefile` for more information on what these commands do.
95
+
Please be sure to review the `makefile` for more information on what this command and others do.
96
+
97
+
If UDOIT is running without errors, you can move on to [installing it for your LMS](#connecting-udoit-to-an-lms)! If you're encountering errors, please check out the [wiki](https://github.com/ucfopen/UDOIT/wiki).
85
98
86
99
### Option 2: Manual Installation
87
100
If you prefer not to use Docker, the process is more complicated:
@@ -140,3 +153,6 @@ For example, if you are setting this up on your local computer via Docker, it ma
140
153
To configure it fully within your LMS, follow the installation instructions below that apply to you.
141
154
- To install it on Canvas, follow [INSTALL_CANVAS.md](INSTALL_CANVAS.md)
142
155
- or for D2l Brightspace, follow [INSTALL_D2L.md](INSTALL_D2L.md)
156
+
157
+
## Encountering Errors
158
+
Please resort to the [wiki page](https://github.com/ucfopen/UDOIT/wiki) for some commonly found errors when setting up UDOIT.
Copy file name to clipboardExpand all lines: INSTALL_CANVAS.md
+56-52Lines changed: 56 additions & 52 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,27 +5,29 @@ Once UDOIT has been installed on a public web server the following steps must be
5
5
* Update the Institutions table
6
6
* Install the application
7
7
8
+
## Docker Compose Base URL
9
+
If you are setting up UDOIT for local development through `docker compose`, <YOUR_UDOIT_BASE_URL> in both the API developer key and the LTI developer key above should be set to `http://127.0.0.1:8000/udoit3`.
10
+
11
+
8
12
## Create an API Developer Key
9
13
UDOIT requires an API developer key since all course data is gathered through the Canvas API.
10
14
11
15
### Steps to Create an API Key
12
16
1. Navigate to `Developer Keys` in the root account menu.
* If your instance of Canvas is self-hosted, modify the URL under **JWK Method** to point to your Canvas instance.
105
+
* Set Additional Settings
106
+
* Domain: Your UDOIT domain
107
+
* Tool ID: Enter a name
108
+
* Custom Fields
109
+
```
110
+
lms_id=canvas
111
+
lms_user_id=$Canvas.user.id
112
+
lms_course_id=$Canvas.course.id
113
+
lms_api_domain=$Canvas.api.domain
114
+
```
108
115
4. Click Save.
109
-
5. Click `ON` to enable the newly created key.
110
-
111
-
---
112
-
## Docker Compose Base URL
113
-
If you are setting up UDOIT for local development through `docker compose`, <YOUR_UDOIT_BASE_URL> in both the API developer key and the LTI developer key above should be set to `http://127.0.0.1:8000/udoit3`.
116
+
5. Click `ON` to enable the newly created key.
114
117
115
-
---
116
118
## Update the Institutions Table
117
119
UDOIT is built to support more than one LMS instance. For this purpose, we have an `institution` table that must be populated with the LMS information.
118
120
@@ -126,17 +128,21 @@ UDOIT is built to support more than one LMS instance. For this purpose, we have
126
128
- `CREATED` = Date in this format: `2021-06-08`
127
129
- `STATUS` = `1` if you are using MySQL or MariaDB (or Docker), `true` if you are using PostgreSQL
128
130
- `VANITY_URL` = Your LMS vanity URL (i.e. `canvas.myschool.edu`)
129
-
-`METADATA` = Optional. Institution-specific settings, such as language or excluded tests. Text representation of a JSON object. (i.e. `{"lang":"es"}`)
131
+
- `METADATA` = Optional. Institution-specific settings, such as language or excluded tests. Text representation of a JSON object. (i.e. `{"lang":"en"}`)
130
132
- `API_CLIENT_ID` = The ID of the developer API key you created earlier
131
133
- `API_CLIENT_SECRET` = The secret for the API key you created earlier
132
134
133
-
4. Run the following command:
135
+
With all the values now set up, you're ready to run the command that will automate the creation of your `institutions` table! Run the following command if you have a MySQL database setup:
136
+
```
137
+
make ins-mysql
138
+
```
139
+
Or this one if you have a PostgreSQL setup:
134
140
```
135
-
make ins-mysql # For MySQL or MariaDB
136
-
make ins-psql # For PostgreSQL
141
+
make ins-psql
137
142
```
143
+
Your database should now show a new row in the `institution` table, containing all the values you input above.
144
+
138
145
139
-
---
140
146
## .ENV Setup
141
147
For cloud-hosted canvas instances, the default value for the `JWK_BASE_URL` environmental variable will work out of the box. If you are not cloud-hosted, you may need to change the value of this variable in `.env.local` to match your canvas instance.
142
148
@@ -154,5 +160,3 @@ UDOIT now needs to be added to an account in Canvas. Follow these steps to add t
154
160
9. Click Submit.
155
161
156
162
You're done! "UDOIT" should now appear in the navigation menu of the course (or every course in the account) in which you installed it. If you installed it on an account, "UDOIT Admin" will also appear in the account navigation menu.
0 commit comments