BigW Consortium Gitlab

  1. 20 Nov, 2014 1 commit
  2. 28 Oct, 2014 1 commit
  3. 01 Oct, 2014 1 commit
  4. 28 Mar, 2014 1 commit
    • Drop all tables before restoring a PostgreSQL DB · 77b57c11
      Jacob Vosmaer authored
      Invoking 'db:schema:load' turned out to be a bad idea: when downgrading
      an existing GitLab installation, the schema of the newer version would
      be preserved when trying to import the old version.
  5. 26 Feb, 2014 1 commit
    • Empty the database during Postgres backup restore · 8fe10e64
      Jacob Vosmaer authored
      The expected behavior during a GitLab backup restore is to overwrite
      existing database data. This works for MySQL because the output of
      mysqldump contains 'DROP TABLE IF EXISTS' statements. pg_dump on the
      other hand assumes that one will restore into an empty database. When
      this is not the case, during the restore with psql some of the data will
      be skipped if existing data is 'in the way'. By first invoking `rake
      db:schema:load` during a Postgres GitLab backup restore, we make sure
      that all important data is correctly restored.
  6. 23 Jan, 2014 1 commit
  7. 06 Nov, 2013 1 commit
  8. 05 Nov, 2013 1 commit
  9. 04 Nov, 2013 1 commit
    • More escaping · c46eaca9
      Nigel Kukard authored
      - Database name may contain characters which are not shell friendly
      - Database password could contain the same
      - While we at it there is no harm in escaping generated paths too
      - Refactored 2-line system(command)
      Signed-off-by: 's avatarNigel Kukard <nkukard@lbsd.net>
  10. 10 Jun, 2013 1 commit
  11. 07 May, 2013 1 commit
  12. 05 Apr, 2013 1 commit