> For the complete documentation index, see [llms.txt](https://userguide.wlanpi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.wlanpi.com/wlan-pi-os/network-info/making-your-own-namespace-configuration.md).

# Making your own Namespace configuration

This guide walks through how namespaces can be setup and managed

As you now know, the WLAN Pi now supports automated management of namespace configuration.

To setup your WLAN Pi with the Namespaces functionality is a 4 step procedure

1. Install & configure the applications you want to run
2. Setup a link to those applications for use by the Namespace functions
3. Create one or more Namespace configuration(s)
4. Activate the configuration of your choice

Steps 1 & 2 are **pre-requisites** which the user must carry out directly on their WLAN Pi. This would usually be done with an SSH session.

Steps 3 & 4 are the **namespace configuration procedure** and can be managed from within the **WLAN Pi application**


---

# 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://userguide.wlanpi.com/wlan-pi-os/network-info/making-your-own-namespace-configuration.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.