As in the labs, you'll be using IntelliJ. Once you've all joined your group using GitHub classroom, you can clone your repository using IntelliJ:
:warning: IDEA will sometimes decide to "help" you by offering
"Compile TypeScript to JavaScript?" :bangbang: Never say "OK" to this
offer -- if you do it will make a complete mess of your project. We're
using other tools (gradle
, yarn
, and ng
) to do that compilation.
If you let IDEA do it, you'll
have a ton of JavaScript files cluttering up your project and confusing other
tools.
localhost:4567
)localhost:9000
)karma
(client-side, Angular) testskarma
(client-side, Angular) tests.
karma
tests and generate test coverage data which will be placed in client/coverage
; open the index.html
in that directory in a browser and you'll get a web interface to that coverage data.karma
tests, but leave the testing browser open and the tests in "watch" mode. This means that any changes you make will cause the code to recompile and the tests to be re-run in the background. This can give you continuous feedback on the health of your tests.seedMongoDB
command is defined in the top level build.gradle
and current loads two files, todos.seed.json
and users.seed.json
, both of which are also in the top level of the project. (They probably should be in a data
directory to reduce clutter, so you might want to move them.) To load new/different data you should create the necessary JSON data files, and then update build.gradle
to load those files.build.sh is a script that calls upon gradle build to build the entire project which creates an executable to be able to launch the
project in production mode. To run build.sh, go to your project directory in a terminal and enter:./build.sh
When build.sh is run, the script .3601_run.sh is copied to ~/3601.sh. When this is launched, for example, ./3601.sh
, will run your project in production mode. The API_URL in environment.prod.ts needs to be
the actual URL of your server. If your server is deployed on a droplet or virtual machine, for example, then you want something like
http://192.168.0.1:4567
where you replace that IP with the IP of your droplet. If you've set up a domain name for your system, you can use that instead, like http://acooldomainname.com
.
:exclamation: Pro-tip: IntelliJ comes with a nice view to see the mongo databases setup. To access this click on File -> Settings -> Plugins, type Mongo and make sure the Mongo Plugin is installed. Now head to View -> Tool Windows -> Mongo Explorer. Then use the tool icon to add configuration. Once prompted type for Path to Mongo Shell: "/usr/bin/mongo" and hit the green :heavy_plus_sign:, to add your label and, huzzah!, Mongo Explorer is on your side bar.
Instructions on setting up the project for production can be found here: UMM CSCI 3601 Droplet Setup Instructions
Testing options are still integrated in this lab so you can test the client, or the server or both. Testing client:
runAllTests
runs both the server tests and the clients tests once.runClientTests
runs the client tests once.runClientTestsAndWatch
runs the client tests every time that the code changes after a save.runClientTestsWithCoverage
runs the client tests and deposits code coverage statistics into a new directory within client
called coverage
. In there you will find an index.html
. Right click on index.html
and select Open in Browser
with your browser of choice. For Chrome users, you can drag and drop index.html onto chrome and it will open it. runE2ETest
runs end to end test for the client side. NOTE: Two Gradle tasks must be run before you can run the e2e tests.
The server (run
) needs to be on for this test to work, and you have to
need to have data in the dev
database before running the e2e tests!Turn on your repo in Travis CI, replace the build status image in this README, and push your changes. That will trigger a build with Travis.