> For the complete documentation index, see [llms.txt](https://data-engineering-zoomcamp-2025-t.gitbook.io/tinker0425/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-engineering-zoomcamp-2025-t.gitbook.io/tinker0425/module-1/1.2-docker-and-docker-compose/docker-compose-summary.md).

# Docker-Compose Summary

Last updated Jan 22, 2025

:writing\_hand: To make sure I was understanding the final version of our Docker lesson, I did two things. I first worked through this quickstart <https://docs.docker.com/compose/gettingstarted/> , which gave me another example of how to use docker-compose. I then went back and made sure I could use the docker-compose YAML file we created.

Thus, I \*think\* these are the steps we need to take if we were starting over:

{% stepper %}
{% step %}

### What is our goal?

:pencil: From you code editor

First, write your code and figure out what your goal is. In our case we are writing a python script `.py` that ingests `.csv` data in postgres. In my repo, I also created an `.env` file to hold our parameters.
{% endstep %}

{% step %}

### Dockerize it!

:pencil: From you code editor

Now we will need a Docker file and a docker-compose file. We use our Docker file to build our environment and you can find a full list of 'dictionary' options online. We use our docker-compose yaml file to create our server and container structures and then we can easily start or end the process in CLI.
{% endstep %}

{% step %}

### View it!

:black\_medium\_small\_square:Terminal & :globe\_with\_meridians: web browser

To view our work on the front end, we need to `docker-compose up -d` to run it and then open it's location on our browser. For our project, we are using local host and port 8080 (for pgAdmin).
{% endstep %}

{% step %}

### Use it!

:globe\_with\_meridians: web browser

Because our project end goal is being able to look at the data using SQL queries in pgAdmin, we now want to use it!&#x20;
{% endstep %}

{% step %}

### End

:black\_medium\_small\_square:Terminal

When you're done with your docker-compose be sure to end it by running `docker-compose down`
{% endstep %}
{% endstepper %}

### Resources

:scroll: My repo for this summary section can be found here:

{% @github-files/github-code-block url="<https://github.com/Tinker0425/de-zoomcamp-my-work/tree/master/module-01/docker/summary>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://data-engineering-zoomcamp-2025-t.gitbook.io/tinker0425/module-1/1.2-docker-and-docker-compose/docker-compose-summary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.