> For the complete documentation index, see [llms.txt](https://kchuene.gitbook.io/data-communication-project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kchuene.gitbook.io/data-communication-project/setup/ubuntu-production-server.md).

# Ubuntu Production Server

The production node.

## VM Overview

| Category         | Specification                                         |
| ---------------- | ----------------------------------------------------- |
| VM Software      | Virtualbox 7.0.16\_Ubuntu r162802 + Guest Additions   |
| Containerization | Docker 29.4.1 build 055a478                           |
| OS Versions      | Ubuntu Server 24.04.4 (LTS), 64-bit                   |
| RAM              | 1280 MB                                               |
| Storage          | 10 GB, Dynamic, SSD enabled                           |
| CPU              | 1                                                     |
| Network Adapter  | Virtualbox Host-only                                  |
| Services         | DVWA v1.9 (HTTPS), OpenSSH 1:9.6p1-3ubuntu13.15 (SSH) |
| User             | prod-admin:prod-admin                                 |

{% hint style="info" %}
Make sure to check the **Install OpenSSH server** option when installing the operating system.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kchuene.gitbook.io/data-communication-project/setup/ubuntu-production-server.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.