> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/operations/web-server.md).

# web server

### Started By

Web server is spawned by [tboamapp](https://prosbcdocs.telcobridges.com/telecom-references/developer-reference/toolpack-api/tboamapp).

### Role

The web server is the main interface of the Toolpack system. Toolpack uses 3rd party web server, Mongrel for Windows and Lighttpd for Linux/Solaris. The web server is manage by [tboamapp](https://prosbcdocs.telcobridges.com/telecom-references/developer-reference/toolpack-api/tboamapp) through [tboamappctrl](/tmedia-documentation/other-pages/operations/tboamappctrl.md).

It allows users to:

* Query the status from the system.
* Query/Modify the configuration stored in a MySQL database.

### High Availability

There are no special mechanism between instances of the web server, they are both independent. When running Toolpack on 2 hosts, both web server instance can read, modify the configuration of the system. If an web server instance crash, it will be restarted by [tboamapp](https://prosbcdocs.telcobridges.com/telecom-references/developer-reference/toolpack-api/tboamapp).

### Logs

* Where the logs are located?

> \[InstallDir]/toolpack/pkg/\[Version]/web/log/ /lib/tb/toolpack/pkg/2.3.1/web/log/ C:\TelcoBridges\toolpack\pkg\2.3.1\web\log


---

# 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://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/operations/web-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.