Commit 0e02daad authored by Job van der Voort's avatar Job van der Voort 🚀

Merge branch 'data-access' into 'master'

Data access

See merge request !4068
parents f34eadf0 c59966d4
Pipeline #5235423 passed with stages
in 10 minutes and 33 seconds
---
layout: markdown_page
title: "Data analysis"
---
### Get a GitLab Linux account
Ask production folks (`#infrastructure` channel) to set up a Linux account for you. Mine is `victor`, and is used as an example below.
### Access `worker1.staging.gitlab.com` staging rails console
Access the server
```
$ ssh victor@worker1.staging.gitlab.com
```
Run
```
$ sudo gitlab-rails c production
```
### Access `db2.staging.gitlab.com` db
As required, ask production folks to refresh the `db2.staging.gitlab.com` db with the `gitlab.com` db.
Access the server
```
$ ssh victor@db2.staging.gitlab.com
```
Run
```
$ sudo gitlab-psql gitlabhq_production
```
### Access `version.gitlab.com` db
Access the server
```
$ ssh victor@version.gitlab.com
```
Use `psql`
```
$ sudo su postgres
$ psql
```
Access the db
```
postgres=# \c version_gitlab_com_production
postgres=# \dt
```
### Access db from a sql client
Access db from a sql client for additional features and ease of use. The sql client can connect to your local machine, and tunnel to the server. A suggested native Mac sql client is [Postico](https://eggerapps.at/postico/). Ask GitLab to expense a license. Download and install.
Set up forwarding through your local machine by running one of the following
```
$ ssh -L5432:localhost:5432 victor@db2.staging.gitlab.com
$ ssh -L5432:localhost:5432 victor@version.gitlab.com
```
#### `db2.staging.gitlab.com`
Find the database password on `db2.staging.gitlab.com`
```
$ vi /etc/gitlab/gitlab.rb
```
Look at `postgresql['sql_password']`.
In your sql client, connect with
```
host: localhost
port: 5432
username: gitlab
password: <password>
database: gitlabhq_production
```
#### `version.gitlab.com`
Find the database login and password on `version.gitlab.com`
```
$ sudo cat /home/gitlab-version/version-gitlab-com/config/database.yml
```
In your sql client, connect with
```
host: localhost
port: 5432
username: gitlab-version
password: <password>
database: version_gitlab_com_production
```
---
layout: markdown_page
title: "Product Areas"
title: "Product areas"
---
GitLab is one integrated product. But to facilitate communication and collaboration, we loosely categorize GitLab into these areas.
......@@ -23,7 +23,7 @@ GD is _less concerned_ about:
* GitLab integration (third-party services)
### Current product development focus
These are the 4 major areas of current focus for product development in GD.
These are the 4 major areas of current focus for product development in GD.
#### _Team collaboration with issue boards_
There is a huge opportunity for GitLab to **move into and disrupt** the space of entrenched competitors in the "project management" space. We have the strategic benefit of being one coherent platform, allowing typical "project management" features to seamlessly flow into the more technical software phases of work. Our focus is to leverage the concept of issue boards to solve many of these team collaboration problems.
......@@ -46,8 +46,8 @@ If a new issue comes in, then we should evaluate its priority according to:
### Scenarios
Product Managers, Project Managers, Business Analysts, and Engineering Managers figure out what needs to be built based on investigation and analysis, which they do themselves and/or work with colleagues on.
They translate these concepts into something one level more concrete.
Product Managers, Project Managers, Business Analysts, and Engineering Managers figure out what needs to be built based on investigation and analysis, which they do themselves and/or work with colleagues on.
They translate these concepts into something one level more concrete.
This is where GD begins.
GD provides the tools to enable these folks to document and collaborate on those concrete ideas.
......@@ -55,11 +55,11 @@ These include issues, commenting, prioritization, and organization features.
UX Designers, Visual Designers, Software Engineers, Test Engineers, and Database Engineers create the product in a more tangible form.
GD allows these folks to collaborate with each other.
This creation is from ideation to shipping the product.
Branching, merge requests, and code review are the main features supporting collaboration.
This creation is from ideation to shipping the product.
Branching, merge requests, and code review are the main features supporting collaboration.
The existing features are focused on the git system and the concept of source control.
The first wave of innovation is making these easier so that engineers don't need to be git experts and they can get a lot done in a browser context.
The next innovation is to jump out of the git paradigm and abstract away from commits and branching.
The next innovation is to jump out of the git paradigm and abstract away from commits and branching.
GD allows all these folks to zoom out and look at the big picture, and zoom back in to focus in on tiny details, depending on the scenario.
We are working to strengthen this zoom in and zoom out dynamic, with milestones and boards being the early stages of this innovation.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment