1. 04 Apr, 2017 1 commit
    • Using Django runserver to serve applications · c1f1dfdb
      Our initial desire to make development look like production by using nginx and supervisor is conflicting with our goal of easing local development pains. Specifically, front-end development requires re-compiling/collecting static assets with every change. Using Django to serve the applications alleviates this pain and allows developers to maintain their current workflows.
      Clinton Blackburn committed
  2. 30 Mar, 2017 2 commits
  3. 28 Mar, 2017 1 commit
  4. 24 Mar, 2017 1 commit
  5. 23 Mar, 2017 2 commits
  6. 16 Mar, 2017 2 commits
  7. 10 Mar, 2017 2 commits
  8. 08 Mar, 2017 1 commit
  9. 24 Feb, 2017 3 commits
  10. 21 Feb, 2017 1 commit
  11. 31 Jan, 2017 1 commit
  12. 30 Jan, 2017 1 commit
  13. 26 Jan, 2017 2 commits
  14. 25 Jan, 2017 8 commits
  15. 24 Jan, 2017 7 commits
  16. 23 Jan, 2017 3 commits
  17. 19 Jan, 2017 1 commit
  18. 05 Jan, 2017 1 commit
    • Updated provisioning script · 6d121004
      - Waiting for MySQL container to come online before provisioning databases
      - Creating superusers for each service
      - Populating countries for the E-Commerce Service
      - Using devstack URLs for the Catalog/Discovery Service partner
      - Compiling static assets for each service (except programs, which has no static assets)
      
      ECOM-6560
      Clinton Blackburn committed