1. 27 Mar, 2017 1 commit
  2. 20 Mar, 2017 1 commit
  3. 18 Mar, 2017 1 commit
    • Stan Hu's avatar
      Fix Error 500 when application settings are saved · 681af5bc
      Stan Hu authored
      Due to a Rails bug, fetching the application settings from Redis
      may prevent the attribute methods from being loaded for the `ApplicationSetting`
      model. More details here: https://github.com/rails/rails/issues/27348
      
      There was also a secondary problem introduced by overriding these
      association methods which caused all default visibility levels to be
      set to `nil`. Before, the previous implementation allowed the string
      "20" to be saved as an integer, while now a table lookup happens
      before that. We fix this by enforcing the integer value in the
      controller and default to PRIVATE.
      
      Closes #29674
      681af5bc
  4. 09 Mar, 2017 3 commits
  5. 07 Mar, 2017 2 commits
  6. 06 Mar, 2017 2 commits
  7. 03 Mar, 2017 2 commits
  8. 01 Mar, 2017 1 commit
  9. 28 Feb, 2017 3 commits
  10. 23 Feb, 2017 5 commits
  11. 19 Feb, 2017 1 commit
  12. 18 Feb, 2017 1 commit
  13. 15 Feb, 2017 3 commits
  14. 08 Feb, 2017 2 commits
  15. 06 Feb, 2017 2 commits
  16. 03 Feb, 2017 1 commit
  17. 31 Jan, 2017 1 commit
    • Kamil Trzcinski's avatar
      Add GitLab Pages · 120f9aba
      Kamil Trzcinski authored
      - The pages are created when build artifacts for `pages` job are uploaded
      - Pages serve the content under: http://group.pages.domain.com/project
      - Pages can be used to serve the group page, special project named as host: group.pages.domain.com
      - User can provide own 403 and 404 error pages by creating 403.html and 404.html in group page project
      - Pages can be explicitly removed from the project by clicking Remove Pages in Project Settings
      - The size of pages is limited by Application Setting: max pages size, which limits the maximum size of unpacked archive (default: 100MB)
      - The public/ is extracted from artifacts and content is served as static pages
      - Pages asynchronous worker use `dd` to limit the unpacked tar size
      - Pages needs to be explicitly enabled and domain needs to be specified in gitlab.yml
      - Pages are part of backups
      - Pages notify the deployment status using Commit Status API
      - Pages use a new sidekiq queue: pages
      - Pages use a separate nginx config which needs to be explicitly added
      120f9aba
  18. 23 Jan, 2017 1 commit
  19. 20 Jan, 2017 1 commit
  20. 12 Jan, 2017 1 commit
    • Horacio Sanson's avatar
      Add support for PlantUML diagrams in Asciidoc. · f986b4c4
      Horacio Sanson authored
      This MR enables rendering of PlantUML diagrams in Asciidoc documents. To add a
      PlantUML diagram all we need is to include a plantuml block like:
      
      ```
      [plantuml, id="myDiagram", width="100px", height="100px"]
      --
      bob -> alice : ping
      alice -> bob : pong
      --
      ```
      
      The plantuml block is substituted by an HTML img element with *src* pointing to
      an external PlantUML server.
      
      This MR also add a PlantUML integration section to the Administrator -> Settings
      page to configure the PlantUML rendering service and to enable/disable it.
      
      Closes: #17603
      f986b4c4
  21. 11 Jan, 2017 3 commits
  22. 29 Dec, 2016 1 commit
  23. 28 Dec, 2016 1 commit