User resource 2

[sibsmc]

Creates a user database called 'ApiUser'
CRUD APIs have been created
A series of tests in Spec have been created for the CRUD APIs

I started to look into authentication, hence these three files:
server/spec/auth/authorize_api_request_spec.rb
server/app/lib/json_web_token.rb
server/app/auth/authenticate_user.rb
however these don't serve any purpose at the moment, no authentication required.

Test can be run by running command 'bundle exec rspec spec'

[sibsmc]

Closed this pull request and pushed changes to original user resource pull request 'Pull Request for User Resource only #75' in order to maintain history.

[nynnejc]

This looks great from my quick glance, @sibsmc. What is the culture around closing our own pull requests? I'm used to a general convention that when you make a PR then you always get someone else to look it over and approve it and only then can you merge. If no one is reacting to your PR, then you can assign them as reviewers. Perhaps you talked about this already i a meeting? If not, I do suggest that we use the chance for reviewing PRs also as a way to learn from each other. Happy to take this discussion over to slack if anyone else have thoughts on it.

[sibsmc]

Hi I think what I wrote above is confusing. I have closed my two new pull requests without merging anything: #134 and #135 , and then I pushed the local changes I had worked on, to my original pull request #75, which is what I should have done instead of opening #134 and #135. PR #75 is not merged and is awaiting review. Definitely agree we should get a review before merging pull requests.