1. 20 Oct, 2018 2 commits
  2. 17 Oct, 2018 1 commit
  3. 19 Jul, 2018 1 commit
  4. 07 Jul, 2018 1 commit
  5. 03 Jul, 2018 1 commit
  6. 02 Jul, 2018 1 commit
  7. 01 Jul, 2018 1 commit
  8. 26 Mar, 2018 1 commit
  9. 01 Mar, 2018 2 commits
  10. 24 Feb, 2018 1 commit
  11. 17 Feb, 2018 1 commit
  12. 15 Feb, 2018 1 commit
  13. 12 Feb, 2018 2 commits
  14. 14 Nov, 2017 1 commit
    • Matthias Larisch's avatar
      Add Codecepton code coverage · 42c18585
      Matthias Larisch authored
      Codecoverage in codeception uses the C3 helper script that needs to be
      included in the site running. This collects code coverage even
      (especially) for acceptance tests, e.g. where codeception itself does
      not have control over the code.
      For coverage collection in general, XDebug is needed and therefore also
      activated.
      
      Production usage not yet possible due to
      https://github.com/Codeception/Codeception/issues/3337 also coverage
      collection is pretty slow.
      42c18585
  15. 02 Nov, 2017 1 commit
  16. 17 Oct, 2017 2 commits
  17. 01 Oct, 2017 1 commit
  18. 28 Sep, 2017 2 commits
  19. 25 Sep, 2017 2 commits
  20. 21 Sep, 2017 1 commit
  21. 28 Aug, 2017 2 commits
  22. 28 Oct, 2016 1 commit
  23. 25 Oct, 2016 1 commit
  24. 13 Oct, 2016 1 commit
    • Nick Sellen's avatar
      Put composers's vendor dir outside of container · 4448e58a
      Nick Sellen authored
      Previously it was inside the container as it seemed a good idea
      to borrow dockers ability to rebuild image when composer.json/lock
      changed.
      
      It has a few downsides though:
      - it was fiddly to update composer deps
      - you cannot see the vendor libs, which is useful for
        - reading, to see what they do
        - IDE debugging to be able to step into code (apparantly)
      
      Additionally, I changed the CI docker containers to not copy the
      app in. Previously it did this as we used docker-in-docker (dind)
      service, which cannot "double mount" volumes, so we had to copy
      instead. We no longer used dind, so no longer an issue.
      4448e58a
  25. 11 Oct, 2016 2 commits
  26. 08 Oct, 2016 1 commit
  27. 06 Aug, 2016 1 commit
  28. 02 Aug, 2016 2 commits
  29. 29 Jul, 2016 2 commits
    • Nick Sellen's avatar
      Add ci, rejig docker config, add generated assets · 0c24eba6
      Nick Sellen authored
      This is quite a big commit based on my ci branch.
      
      ci
      
      works with gitlab ci now, uses docker-in-docker and
      docker-compose to reuse most of the dev/test setup
      
      rejig docker config
      
      I moved all config into docker directories to keep
      it a bit neater, there were getting a lot of files
      in the root dir. It's a bit more annoying to specify
      the paths, but all the scripts/* work just the same
      as before.
      
      add generated assets
      
      I didn't want to add these, but it is tricky to
      build them ready for test, as you need an app server
      up and running. At some point they could be generated
      by a simple script and could be removed again.
      This might cause a bit of hassle when deploying to
      an existing production deployment as it will have
      existing asset files not from git.
      0c24eba6
    • Nick Sellen's avatar
      Update docker-compose to specify chat host · 61261b25
      Nick Sellen authored
      61261b25
  30. 28 Jul, 2016 1 commit