Integration of PostgreSQL and pgAdmin Containers with Docker Compose

To integrate PostgreSQL and pgAdmin using Docker Compose, start by creating a compose.yaml file with the following content:

services:

  postgres:

    image: postgres

    environment:

      POSTGRES_PASSWORD: password


  pgadmin:

    image: dpage/pgadmin4

    environment:

      PGADMIN_DEFAULT_EMAIL: pg@ad.min

      PGADMIN_DEFAULT_PASSWORD: password

    ports:

      - "12345:80"

Save the code above into a file named compose.yaml on your computer. Then, open your terminal, navigate to the directory containing the file, and run the command docker compose up. Wait for Docker to create and start the containers.

Once the containers are running, open your browser and go to http://localhost:12345. You will be prompted to log in to pgAdmin. In the "Email Address / Username" field, enter pg@ad.min as specified in the compose.yaml file, and in the "Password" field, enter password. Click "Login" to access the pgAdmin dashboard.

After logging in, go to the "Register Server" screen, following the steps shown in the image below.

The "Name" field in the "General" section is required, but you can choose any name. In this case, we will choose the name db.
In the "Connection" section, fill in the "Host name/address" field with postgres (this is the DNS name automatically created when the compose is started. Docker directs it to the correct IP address, commonly 172.18.0.2, for example). The "Username" field should be set to postgres, and the "Password" field should contain the text password.

Click "Save".

Comentários

Postar um comentário

Postagens mais visitadas deste blog

Safely Refactoring Endpoints with Postman Tests

Imagem
Refactoring endpoints is a common task in development, but it always requires caution to ensure the expected behavior remains unchanged. With Postman, you can validate changes by comparing responses before and after the refactoring. Step 1: Creating a New Environment Create a new environment in Postman and set it as active. This will store all your variables for use in requests and tests. Step 2: Setting Up the Main Collection Create a collection to store the requests before the code changes. Name it "main". For each request, add a post-response script in the "Scripts" tab to save the response payload to a variable. Use the code below, adjusting the variable name for each request: pm.environment.set("variableName", JSON.stringify(pm.response.json())); Note: Replace variableName with a unique identifier for each request. Step 3: Setting Up the Test Collection Create a second collection, named "staging", to store the requests after the code change...
Leia mais

Views and Functions in PostgreSQL

Views and Functions in PostgreSQL streamline SQL query management, with Views suited for fixed queries and Functions offering flexibility through parameter support. Views A View is a virtual table that stores an SQL query. It does not occupy disk space and always returns real-time data based on the stored query. However, Views do not allow the use of parameters, which limits their flexibility. Example of a View to summarize client data: CREATE VIEW client_summary AS ( SELECT client.id, client.name, client.contact, client_amount.total FROM client JOIN ( SELECT sale.client_id, SUM(sale.amount) AS total  FROM sale  GROUP BY sale.client_id ) AS client_amount  ON client.id = client_amount.client_id WHERE client.id = 1 ); This View works only for a fixed client ID. In this case, 1. Functions Functions provide greater flexibility, accepting parameters and using the PL/pgSQL language. They can return values of different types, such as tables. Example of a Fun...
Leia mais