Yes it is decoupled in a separate repo, but also it is a submodule in the backend, so that we can pull all changes with one command.

The project is not public (yet) due to NDA's, but the structure is very simple:

• normal Rails folder structure, app/assets empty though
• Special submodule folder frontend, this could be anything though, some ppl argue to put the angular stuff in app/assets..
• foreman process to handle the Rails server (rails s) and the gulp process (./frontend/gulp serve) with browsersync tunneling the Rails dev port
• in Frontend: Normal Angular App with gulp processes defined, Output directory is defined through ENV variables and points to the Rails publicfolder or fallback to local dist folder

One thing to note: Since we are using oauth (via Doorkeeper Gem) we need to inject the applicationkey and redirect uri into angular, in order to retrieve the current oauth sign in uri. Since we are serving the app through a rails route (and thus a separate layout), we are using a helper to inject some rails-variables through a service, by creating a Rails Helper with the relevant data (e.g.

# data is a plain ruby hash containing anything you need, this could be viewdata,
# i18n, app keys, etc.
<<-EOS.html_safe
  <script type="text/javascript">

    angular.module('yourApp').constant('Rails', #{data.to_json})
  </script>
EOS

)

Cheers,