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
Edit `docker/nginx.conf`' to point to the UDOIT docker-machine's IP address by replacing both instances of
37
+
Edit `docker/etc/nginx/nginx.conf`' to point to the UDOIT docker-machine's IP address by replacing both instances of
38
38
39
39
```
40
40
localhost
@@ -49,7 +49,7 @@ with
49
49
Generate SSL certificates according to the naming scheme located in the nginx.conf file (`nginx.key` and `nginx.crt`) or use your own SSL certificates:
Copy file name to clipboardExpand all lines: README.md
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,15 +164,19 @@ In order for UDOIT to scan YouTube videos for closed captioning, you will need t
164
164
4. Create an ***API key*** credential.
165
165
5. Add the key to `config/localConfig.php` in the `define('GOOGLE_API_KEY', '');` statement. For example, if your API key is `heythisisanapikey`, that line should look like `define('GOOGLE_API_KEY', 'heythisisanapikey');` when you're done.
166
166
167
+
If you do not provide a Google API key, a warning log will be recorded in `config/log.log` and all YouTube videos will be marked for manual inspection by the user.
168
+
167
169
### Vimeo API Key
168
170
In order for UDOIT to scan Vimeo videos for closed captioning, you will need to create a Vimeo API key. Follow the instructions below:
169
171
170
172
1.[Create a new App on Vimeo Developer API](https://developer.vimeo.com/apps/new?source=getting-started), please note you must have a Vimeo Developer account.
171
173
2. On your applications "Authentication" page, Generate a new Access Token. (Select the `Public` and `Private` checkboxes for Scopes.)
172
174
3. Add the key to `config/localConfig.php` in the `define('VIMEO_API_KEY', '');` statement. For example, if your API key is `heythisisanapikey`, that line should look like `define('VIMEO_API_KEY', 'heythisisanapikey');` when you're done.
173
175
176
+
If you do not provide a Vimeo API key, a warning log will be recorded in `config/log.log` and all Vimeo videos will be marked for manual inspection by the user.
177
+
174
178
### Google Analytics
175
-
If you would like to use Google Analytics for tracking usage of UDOIT, create a new tracking code and add it to `config/localConfig.php` in the `define('GA_TRACKING_CODE', '');` statement. For example, if your tracking code is `UA-12345678-1`, that line should look like `define('GA_TRACKING_CODE, 'UA-12345678-1');` when you're done.
179
+
If you would like to use Google Analytics for tracking usage of UDOIT, create a new tracking code and add it to `config/localConfig.php` in the `define('GA_TRACKING_CODE', '');` statement. For example, if your tracking code is `UA-12345678-1`, that line should look like `define('GA_TRACKING_CODE', 'UA-12345678-1');` when you're done.
176
180
177
181
### Installing the LTI in Canvas
178
182
Log into Canvas to add UDOIT:
@@ -191,10 +195,10 @@ Log into Canvas to add UDOIT:
191
195
#### LTI Config URL Notes
192
196
The URL of your UDOIT LTI config depends on your webserver install. The file is located the `public` directory. The examples below should give you are some possible values:
193
197
194
-
*`http://<DOMAIN>/udoit.xml.php`
195
-
*`http://<DOMAIN>/public/udoit.xml.php`
196
-
*`http://<DOMAIN>/udoit/udoit.xml.php`
197
-
*`http://<DOMAIN>/udoit/public/udoit.xml.php`
198
+
*`https://<DOMAIN>/udoit.xml.php`
199
+
*`https://<DOMAIN>/public/udoit.xml.php`
200
+
*`https://<DOMAIN>/udoit/udoit.xml.php`
201
+
*`https://<DOMAIN>/udoit/public/udoit.xml.php`
198
202
199
203
## Upgrading UDOIT
200
204
The instructions below are general guidelines for upgrading your installation of UDOIT from one version to the next. However, the release notes for a particular version might contain specific instructions for that version, and those instructions supersede the ones below. Since the instructions differ depending on how you installed UDOIT, they are separated by these methods below.
@@ -247,6 +251,12 @@ If database migrations fail, make sure the database user has the ability to alte
247
251
248
252
## FAQs
249
253
254
+
### How do I get in touch with you if I have questions?
255
+
There are a few different ways you can get in touch with us, depending on what you're most comfortable with:
256
+
*[Canvas Community](https://community.canvaslms.com/groups/accessibility) - The easiest option is to comment on the blog post for your version of UDOIT.
257
+
*[Slack](https://ucf-open-slackin.herokuapp.com/) - We have channels for all of our open source projects, including UDOIT.
258
+
* Email - If you're more comfortable with email, you can contact me directly at [jacob.bates@ucf.edu](mailto:jacob.bates@ucf.edu).
259
+
250
260
### How much time will I have to spend maintaining UDOIT?
251
261
UDOIT should require little to no maintenance. It is up to your institution to choose when you update UDOIT to the latest release. UDOIT can be updated by running `git pull` on this repository.
0 commit comments