> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/floating-server/floating-server-v2/running-and-administration.md).

# Running & Administration

### Starting the Server

Once your configuration file is ready, you can start the Floating Server in one of the following ways:

#### Method 1: Executable

If you are using the executable, run the binary matching your operating system:

```bash
./floating-server
```

#### Method 2: Docker

{% stepper %}
{% step %}

### Pull the image

```bash
docker pull licensespring/floating-server-v2:v2.5.1
```

{% endstep %}

{% step %}

### Set up PostgreSQL

* Start a PostgreSQL instance (local or containerized).
* Note the `host`, `port`, `username`, `password`, and `database` name.
* Update your configuration file with these details.
  {% endstep %}

{% step %}

### Prepare configuration and certificates

* Place the configuration file in a local directory.
* Place certificates in another directory.
  {% endstep %}

{% step %}

### Run the container

Mount both the configuration and certificate directories so that the container has access:

```bash
docker run -d  \
--name fsv2 \
--network fsnet \
-v /path/to/config:/app/config \
-v /path/to/certs:/app/certs \
-p 8080:8080 \
licensespring/floating-server-v2:v2.5.1
```

{% endstep %}

{% step %}

### Notes

* Replace `/path/to/config` with your config directory.
* Replace `/path/to/certs` with your certificates directory.
* Adjust `-p` if exposing on a different port.
  {% endstep %}
  {% endstepper %}

{% hint style="success" %}

* **Replace** /path/to/config with your config directory.
* **Replace** /path/to/certs with your certificates directory.
* **Adjust** `-p` if exposing on a different port.
  {% endhint %}

#### Method 3: Docker Compose

A prebuilt `docker-compose.yml` is included in the documentation. Running it sets up both PostgreSQL and the Floating Server in one step:

```bash
docker-compose up -d
```

This is the fastest way to get everything running.

### First-Time Admin Setup

When the server starts for the first time, no users or admins exist. You must set the initial **admin password**.

{% hint style="info" %}

* Default username: **admin**
* **Password:** defined during setup.
  {% endhint %}

#### Setting the Password

You can set it via:

{% stepper %}
{% step %}

### UI

Navigate to the Floating Server’s URL. You’ll be redirected to the password setup page.

![Running the Floating Server for the first time: Setting initial Admin Password](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/sWQDFYAjGFJuMOwnuiPS/6CLcmIv1QNNDgKDDEXj7l%20sidn6wAKJjd6RBOYzC6Hf%2020250808%20015307.png)
{% endstep %}

{% step %}

### API

Call the endpoint:

```http
POST /api/v5/auth/initial-password
```

{% endstep %}
{% endstepper %}

**Request body:**

```json
{
  "password": "string"
}
```

**Responses:**

| Code  | Description                                    |
| ----- | ---------------------------------------------- |
| `200` | Password set successfully  returns a JWT token |
| `400` | Invalid input                                  |
| `401` | Authentication failed                          |

#### Logging In

Once the initial password is set:

* Log in using `admin` and your chosen password.
* You will then access the Floating Server admin panel.

![Image of the Floating Server Running](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/ng60hmxJrhqBl5X4ytjw/4HXLLr5Q7QtA2dEoLTkx7_image.png)

* From here, you can create additional user accounts.

{% hint style="info" %}
After starting the server:

* **Executable:** A log file is generated automatically.
* **Docker:** Use `docker logs` to view server output.
  {% 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://docs.licensespring.com/floating-server/floating-server-v2/running-and-administration.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.