initialise elm application with routes #2
Conversation
| - Clone this repository: `git clone git@github.com:dwyl/app-mvp-elm.git && cd app-mvp-elm` | ||
| - Install elm-live, see https://github.com/wking-io/elm-live | ||
| - Run `elm-live src/Main.elm --pushstate -- --outpute elm.js --optimize` see https://github.com/dwyl/learn-elm/issues/156 | ||
| - Visit localhost:8000 to see the application |
There was a problem hiding this comment.
consider adding more docs on what the person should expect to see when they boot the App. 💭
| @@ -0,0 +1,6099 @@ | |||
| (function(scope){ | |||
There was a problem hiding this comment.
@SimonLab do we want to be adding the (compiled) elm.js file to GitHub?
is it not redundant if people are using elm-live to run it?
There was a problem hiding this comment.
At the moment unfortunately I need this file to be on the commits.
I'm using it on Heroku and I haven't find a way to create this file on compilation with the Heroku static buildpack yet.
There was a problem hiding this comment.
oh ... 💭
The way we did it on OA was to compile it on CI and upload the compiled file to S3. 💡
But that's overkill for this MVP (for now).
OK. let's just merge the compiled file for now.
There was a problem hiding this comment.
I'm using the same method to deploy Elm as described here: dwyl/elm-pwa-example#3 (comment)
ref: #1
Create the Elm application which manages three routes (for now): home page, authentication page and 404 page.
Testing the different endpoint are parsed correctly: "/" and "/auth"