-
Notifications
You must be signed in to change notification settings - Fork 3
Development Notes
This page contains notes as a developer I'm collecting as I go.
Trying out the Codacy service.
To get an additional opinion on the static analysis, I ran Plato against the project. I'm new to Codacy, so this was an step that connected my past tools with the new, and helps me evaluate Codacy.
I'm opting for using global plato, npm install -g plato, to keep development tools running on git hooks, cloud based, and out of the project source as much as possible. Referring to plato analysis is just putting a past perspective forward on the state of the source for me. Here is the main command I used to generate the report (run from the project root directory):
plato -r -d reports/plato -l .jshintrc -t "Flux-React-Example" -x 'node_modules\/*|dist\/*|assets\/*|reports\/*|tmp\/*|Gruntfile.js' ./**When the flux-react-example creates a contact, it calls the Contact Service. On the server, the Contact Service inserts a new contact into an AMQP compliant queue, which is picked up by a queue consumer worker process. When a new contact is inserted into the queue, the queue consumer worker is notified and it sends the mail using a well-known mail service.
The flux-react-example mail service relies on node packages:
These are configured for flux-react-example in configs/mail.
In development mode, flux-react-example defaults to post outgoing mail to a local AMQP broker. If one does not exist, in the browser you should get a 400 response from the POST that creates a new contact. If one does exist, the new contact is added to the queue. You can run the contact worker process to send the queued mail message to a well-known mail service.
Here is what I did to setup the AMQP queue on my development machine: