title: Splitting Single Page App code from Phoenix Backend?
body: <p>I'm working on a Phoenix + ReactJS app and so far all the tutorials I've seen on the internet seem to install React inside the Phoenix directory:</p>
  
  <ul>
  <li><a href="https://blog.diacode.com/trello-clone-with-phoenix-and-react-pt-1" rel="nofollow">Trello Clone</a></li>
  <li><a href="https://medium.com/@diamondgfx/phoenix-v1-1-2-and-react-js-3dbd195a880a#.8fr24l1xp" rel="nofollow">React + Phoenix</a></li>
  <li><a href="https://hashrocket.com/blog/posts/integrating-react-components-with-a-phoenix-application" rel="nofollow">Integrating React Components in Phoenix - HashRocket</a></li>
  <li><a href="http://elixirsips.com/episodes/183_react_with_phoenix.html" rel="nofollow">React + Phoenix - Elixir Sips</a></li>
  <li><a href="http://10consulting.com/2015/11/18/phoenix-react-redux-example/" rel="nofollow">Phoenix React Redux example by 10 consulting</a></li>
  </ul>
  
  <p>Now I have 2 questions regarding this:</p>
  
  <ul>
  <li><p>first of all, is it a good ideea?
  Most SPA projects I've worked on had their client side code split from the backend code.
  There are also several <a href="https://quickleft.com/blog/six-reasons-we-split-front-end-and-back-end-code-into-two-git-repositories-working-with-github-repositories/" rel="nofollow">advantages</a> to doing it this way.
  Why do Phoenix developers tend to go the other way around?</p></li>
  <li><p>if we do separate the frontend from the backend how should we actually do it? What are we supposed to configure and how?</p></li>
  </ul>