gio at Internet Archive

Updates from February, 2016 Toggle Comment Threads | Keyboard Shortcuts

• 

  gio 12:08 am on February 25, 2016 Permalink  

  GitLab 8.5 and the new CI 

  With GitLab 8.5 we are introducing some great new features, between them also a brand new CI service.

  To have a working CI follow this quick start.

  If you don’t know how to setup your runner or you need one: ask me. We have a VM with docker available to register new runners.

   
• 

  gio 11:35 pm on February 24, 2016 Permalink  

  Docker cookbook 

  :: list images

  sudo docker images

  sudo docker images

  :: list the containers

  sudo docker ps sudo docker ps -a

  sudo docker ps sudo docker ps -a

  :: start/stop a container

  sudo docker start CONTAINER

  sudo docker start CONTAINER

  (More …)

   
• 

  gio 11:53 pm on February 23, 2016 Permalink  

  GitLab: installing version 8.5.0 

  • One:

    sudo apt-get install curl openssh-server ca-certificates postfix

    sudo apt-get install curl openssh-server ca-certificates postfix

  • Two:

    ~$ curl -s https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash ~$ sudo apt-get install gitlab-ce=8.5.0-ce.1

    ~$ curl -s https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash ~$ sudo apt-get install gitlab-ce=8.5.0-ce.1

  • Three:

    sudo gitlab-ctl reconfigure

    sudo gitlab-ctl reconfigure

   
• 

  gio 8:51 pm on February 23, 2016 Permalink  

  GitLab: bakup and restore 

  WARNING: You can only restore a backup to exactly the same version of GitLab that you created it on.
  

  :: Create a backup of the GitLab system:

  • sudo gitlab-rake gitlab:backup:create

    sudo gitlab-rake gitlab:backup:create

    the backup file will be created at /var/opt/gitlab/backups/
    or where specified in the gitlab config file.

    You can skip the backup for come components using:

    sudo gitlab-rake gitlab:backup:create SKIP=db,uploads

    sudo gitlab-rake gitlab:backup:create SKIP=db,uploads

  • Please be informed that a backup does not store your configuration files. One reason for this is that your database contains encrypted information for two-factor authentication. Storing encrypted information along with its key in the same place defeats the purpose of using encryption in the first place!
    At the very minimum you should backup /etc/gitlab/gitlab-secrets.json (Omnibus) or /home/git/gitlab/.secret (source) to preserve your database encryption key.

  :: Restore a previously created backup:
  • We will assume that you have installed GitLab from an omnibus package and run

    sudo gitlab-ctl reconfigure

    sudo gitlab-ctl reconfigure

    at least once.

    Note: that you need to run gitlab-ctl reconfigure after changing gitlab-secrets.json.

    First make sure your backup tar file is in /var/opt/gitlab/backups (or wherever gitlab_rails[‘backup_path’] points to).

    sudo cp 1393513186_gitlab_backup.tar /var/opt/gitlab/backups/

    sudo cp 1393513186_gitlab_backup.tar /var/opt/gitlab/backups/

  • Next, restore the backup by running the restore command. You need to specify the timestamp of the backup you are restoring.

    # Stop processes that are connected to the database sudo gitlab-ctl stop unicorn sudo gitlab-ctl stop sidekiq   # This command will overwrite the contents of your GitLab database! sudo gitlab-rake gitlab:backup:restore BACKUP=1393513186   # Start GitLab sudo gitlab-ctl start   # Check GitLab sudo gitlab-rake gitlab:check SANITIZE=true

    # Stop processes that are connected to the database sudo gitlab-ctl stop unicorn sudo gitlab-ctl stop sidekiq # This command will overwrite the contents of your GitLab database! sudo gitlab-rake gitlab:backup:restore BACKUP=1393513186 # Start GitLab sudo gitlab-ctl start # Check GitLab sudo gitlab-rake gitlab:check SANITIZE=true

  source: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/raketasks/backup_restore.md