Upgrade to Phoenix version 1.4

[RobStallion]

• [x] Upgrade version of phoenix from 1.3 to 1.4

Steps to upgrade can be frond in here

[RobStallion]

Phoenix 1.4 uses Jason in favour of Poison as Chris says in his upgrade guide

Phoenix 1.4 uses Jason for json generation in favor of poison. Poison may still be used, but you must add :poison to your deps to continue using it on 1.4. To use Jason instead, :jason to your deps in mix.exs:

This is not mandatory and as we are using both poison and httpoison in the project I will leave them in the list of deps for the meantime.

These deps are used for storing and retrieving data from S3, something which may not be needed in the future (see #126). If and when we change the way we store data, we can change this step also.

[RobStallion]

Upgrade has gone fine up until Replace Brunch with webpack

When I got to this stage the css in the application did not appear to be loading correctly. All the text sizing was too big. I could not see any errors however so it was not clear what was causing this issue. Having webpack is an optional feature of phoenix 1.4 so I am going to open a separate issue on this and come back to this at a later date.

[nelsonic]

@RobStallion are we using brunch/webpack for anything?

[RobStallion]

At the moment brunch is just being used in the default way all phoenix applications use it.

Copying all static files into priv/static (one css file, the phoenix_html node_module and static assets (images etc))

[RobStallion]

Closing as upgrade has been merged in