> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/apma/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/apma/services/apache.md).

# Apache Web Hosting

The Apache web server hosts seminars and interest group sites like [www.dam.brown.edu/siam](http://www.dam.brown.edu/siam). It is separate from the general Applied Math site that can be found at [appliedmath.brown.edu](https://appliedmath.brown.edu/).

The pages are HTML-coded and are managed by uploading new content files through SFTP. Faculty members can request access for themselves and others that would assist in managing the sites.

## Required Software

An SFTP client is required to upload new content to the server. [Filezilla](https://www.brown.edu/information-technology/software/catalog/filezilla) is available on the Brown software page and supports Windows, Mac, and Linux.

The [Brown VPN](https://it.brown.edu/services/virtual-private-network-vpn) is required to access to server from off-campus.

## Uploading Content

1. Off-campus users must first connect to the [Brown VPN](https://ithelp.brown.edu/kb/articles/get-started-with-brown-s-vpn-virtual-private-network).
2. In Filezilla, click **File** > **Site** **Manager**.
3. Click **New Site,** enter “**DAM web**” as the name.

   `Protocol: SFTP`

   `Host: www.dam.brown.edu`

   `Port: 22`

   `Logon Type: Interactive`

   `User: <your-username>`
4. On the **Advanced** tab, set **Default remote directory** to `/www.dam/htdocs`
5. Click **Connect**.
   1. Click **OK** to accept the server host key.
   2. Enter your Password and click **OK**.
   3. You may be prompted to select a Duo authentication method. Enter the number of your choice and click **OK**. (Note: this looks very similar to a password prompt.)
6. In the right pane (Remote site) the web directories are listed. Navigate to the folder of your site.

<figure><img src="https://3275110800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAyXYvu8Nmxx8GSuMZQrQ%2Fuploads%2FJyi2lJvt4rtn12KLbDZZ%2Funknown.png?alt=media&amp;token=7888b7bf-0072-476e-b904-32edf62f24bc" alt="Filezilla folder listing"><figcaption></figcaption></figure>

7\. Upload files by dragging them from your local computer (left pane) to the server (right pane).


---

# 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://docs.ccv.brown.edu/apma/services/apache.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.
