I use elm-live just for compiling the Elm into Javascript and serving me the page with the JS in it.
For everything else I make HTTP calls to my "real" API server (with CORS configured appropriately). This is for a single page application (SPA) rather than something with multiple different pages with Elm components though. On Fri, Nov 4, 2016 at 10:21 AM, Witold Szczerba <[email protected]> wrote: > Hi there, > I have a question about using elm-reactor, elm-live or similar things. I > am creating a "login" application while learning Elm basics. The elm-live > is helping me with first steps, so far I have a working form with JSON HTTP > request. > > Now I am writing a backend server to handle the request. I was hoping to > have things like reverse proxy in elm-reactor or elm-live, so it can > forward the "HTTP POST /login" to the backend I am working on, but this is > not the case. It seems like my only option would be to do it other way > around, so my real server would forward to reactor/live when in dev mode. > Or create third HTTP server so it would forward to the backend or frontend > based on patterns. > > How are you using the elm-reactor or elm-live during development? Are they > meant to be just a helping hand for first contact with Elm? Do you create > your own proxy servers to "join" backend with frontend? Or something else? > > Thanks, > Witold Szczerba > > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
