An error occurred fetching the project authors.
  1. 02 Aug, 2016 1 commit
  2. 28 Feb, 2016 1 commit
  3. 11 Feb, 2016 1 commit
    • Kirill Smelkov's avatar
      gitlab: Slapos'ify gitlab config updates · 468d7934
      Kirill Smelkov authored
      Slapos'ify config updates brought by sync with omnibus-gitlab (see merge
      in the previous patch). Changes:
      
      - default visibility levels gone away (see merge commit and
        https://gitlab.com/gitlab-org/omnibus-gitlab/commit/b5ebbab3 )
      
      - there are new settings for GitLab Pages and Elasticsearch, which are EE
        only and thus we do not support them.
      
      - there are new settings for auxiliary cron-like jobs, which we do not
        support for now, since they are used either for CI (not supported by
        us) or EE features.
      
      Configuration files that were synced, but did not changed are also
      marked as updated, so it is easier to track their changes to upstream in
      the future.
      
      /cc @kazuhiko, @jerome
      468d7934
  4. 17 Jan, 2016 2 commits
    • Kirill Smelkov's avatar
      gitlab/database.yml: Tweak to integrate gitlab with internal postgresql · a73d20f4
      Kirill Smelkov authored
      We tweak database.yml to point to our postgresql unix socket; set
      adapter to hardcoded postgresql, encoding to unicode and omit collation
      (which according to omnibus-gitlab is used for mysql only).
      
      The only instance parameter imported from omnibus is `db_pool` - how
      many connection to a DB to keep open in a RoR thread/process.
      
      XXX we use db's superuser as a user to connect. Is it ok to do even if
          the whole DB is used only for gitlab? (I think it is ok for the
          first iteration, but we'll probably need to refine this later)
      
      /cc @kazuhiko, @jerome
      a73d20f4
    • Kirill Smelkov's avatar
      gitlab: Hook gitlab- and gitlab-shell- configuration files into the system · 13169cab
      Kirill Smelkov authored
      - Download them on SR build and pass info to instance
      - Instance prepares to process them as jinja2 templates
      - Instance hooks the files into configuration location as appropriate
      
      Every file so far is renamed *.erb -> *.in and a header added showing
      that this file is autogenerated with links about what was the base
      gitlab and/or omnibus version and omnibus reference revision this
      template was last updated for.
      
      So far all result configuration files are invalid - because ERB syntax
      is there. We will convert the configuration files to proper jinja2
      syntax and to using slapos parameters incrementally in the upcoming
      patches.
      
      NOTE (again): md5 sums are not yet fixed - we will fix them in the end
          of gitlab patches series after applying all tweaking changes.
      
      /cc @kazuhiko, @jerome
      13169cab