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: CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ If you are outside of UCF, you will need to fork the UDOIT project in order to w
47
47
48
48
### Dev Branches
49
49
50
-
* Naming Convention: `dev/v1.2.10` - a new one for every upcoming release version
50
+
* Naming Convention: `dev/v1-2-10` - a new one for every upcoming release version. (Note: Hyphens are used instead of periods to preserve compatibility with the Heroku button.)
51
51
* Issue branches merge into this branch (never master)
52
52
* When this dev branch is ready for release, it is merged into master and deleted
53
53
@@ -81,8 +81,8 @@ This section is mainly for the project managers, but is here for documentation p
Copy file name to clipboardExpand all lines: HEROKU.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,4 +124,9 @@ If you need to check that the tables exist, you can connect to Postgres using so
124
124
If needed, you can manually run the table creation script: `heroku run composer dbsetup`
125
125
126
126
## Table Schema
127
-
The table schema can be found in [bin/db_create_tables.php](bin/db_create_tables.php)
127
+
The table schema can be found in [migrations/](migrations/)
128
+
129
+
# FAQ
130
+
131
+
## Why aren't my scans completing?
132
+
If you are using the free tier, you may need to manually turn on the worker dyno. You can do this by going to the [Heroku Control Panel](https://dashboard.heroku.com/apps), selecting your instance of UDOIT, clicking **Configure Dynos**, clicking the pencil icon next to the **Worker** dyno, clicking the slider to the **on** position, then clicking **Confirm**.
To create the required tables, run the creation script below. You'll need to complete the db steps above first.
126
126
127
127
```
128
-
$ php composer.phar dbsetup
128
+
$ php composer.phar db-setup
129
129
```
130
130
131
131
The table schema can be found in [bin/db_create_tables.php](bin/db_create_tables.php)
@@ -261,7 +261,7 @@ For quick local development, set `$UDOIT_ENV = ENV_DEV;` in `config/localConfig.
261
261
From the public directory, run:
262
262
263
263
```
264
-
$ php -S localhost:8000
264
+
$ php composer.phar start
265
265
```
266
266
267
267
Then open [http://localhost:8000 in a browser](http://localhost:8000).
@@ -270,13 +270,19 @@ Then open [http://localhost:8000 in a browser](http://localhost:8000).
270
270
We use phpunit to run unit tests on UDOIT. To run the tests, type the following command:
271
271
272
272
```
273
-
$ ./vendor/phpunit/phpunit/phpunit
273
+
$ php composer.phar test
274
+
```
275
+
276
+
We included a Dockerfile, docker-compose.yml, and tests script to run your tests in a predictable environment. To run tests using docker run this command:
277
+
278
+
```
279
+
$ php composer.phar docker-test
274
280
```
275
281
276
-
By default, phpunit will run all tests, including the functional tests that require access to outside APIs. If you would like to exclude those tests, run this command:
282
+
By default, we exclude functional tests that include external APIs. If you would like to run those tests, run this command:
0 commit comments