> For the complete documentation index, see [llms.txt](https://antsankov.gitbook.io/go-live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://antsankov.gitbook.io/go-live/usecases/defaults.md).

# Local Development Server

## Serving an HTML Folder

```
cd my-html-project && go-live
```

{% hint style="info" %}
The index.html file will always be served at the the root as a default.
{% endhint %}

One you're serving the directory, a browser window should pop up, and you will see the server hosting all of the files in the directory, including subdirectories.

To use a different directory, you can the `--dir` flag, like below: 

```
go-live --dir ./my-html-project/
```

\
All relative URL paths in CSS or JS will work. You should see a server CLI dashboard. Any changes you make are not-cached and a refresh will show the new files.

![Running a Server](/files/-MIGEUN0fdMxaHKpQLzm)

If the server allows outbound traffic, it is accessible from the internet or other devices on the subnet.


---

# 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://antsankov.gitbook.io/go-live/usecases/defaults.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.