Commit ca17296d authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'eduardobonet-master-patch-26322' into 'master'

Documentation on connecting GUIs to the database

See merge request gitlab-org/gitlab!69206
parents 243177f3 d77b9b81
...@@ -70,6 +70,36 @@ bundle exec rails db -e development ...@@ -70,6 +70,36 @@ bundle exec rails db -e development
- `SELECT * FROM schema_migrations WHERE version = '20170926203418';`: Check if a migration was run - `SELECT * FROM schema_migrations WHERE version = '20170926203418';`: Check if a migration was run
- `DELETE FROM schema_migrations WHERE version = '20170926203418';`: Manually remove a migration - `DELETE FROM schema_migrations WHERE version = '20170926203418';`: Manually remove a migration
## Access the database with a GUI
Most GUIs (DataGrid, RubyMine, DBeaver) require a TCP connection to the database, but by default
the database runs on a UNIX socket. To be able to access the database from these tools, some steps
are needed:
1. On the GDK root directory, run:
```shell
gdk config set postgresql.host localhost
```
1. Open your `gdk.yml`, and confirm that it has the following lines:
```yaml
postgresql:
host: localhost
```
1. Reconfigure GDK:
```shell
gdk reconfigure
```
1. On your database GUI, select `localhost` as host, `5432` as port and `gitlabhq_development` as database.
Alternatively, you can use the connection string `postgresql://localhost:5432/gitlabhq_development`.
The new connection should be working now.
## Access the GDK database with Visual Studio Code ## Access the GDK database with Visual Studio Code
Use these instructions for exploring the GitLab database while developing with the GDK: Use these instructions for exploring the GitLab database while developing with the GDK:
......
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