docs: cleanup installation

2025-07-01 21:52:58 +00:00 · 2025-06-29 15:53:02 +02:00 · 2025-06-29 15:53:02 +02:00 · 364f391017
commit 364f391017
parent c13861e13c
1 changed files with 55 additions and 51 deletions
--- a/www/docs/installation.md
+++ b/www/docs/installation.md
@ -1,76 +1,68 @@
 # Installation

-File Browser is a single binary and can be used as a standalone executable. Although, some might prefer to use it with [Docker](https://www.docker.com) or [Caddy](https://caddyserver.com), which is a fantastic web server that enables HTTPS by default. Its installation is quite straightforward independently on which system you want to use.
+File Browser is a single binary and can be used as standalone executable. However, it is also available as a [Docker](https://www.docker.com) image. The installation and first time setup is quite straightforward independently of which system you use.

-## Quick Setup
+## Binary

-The quickest way for beginners to start using File Browser is by opening your terminal and executing the following commands:
+The quickest and easiest way to install File Browser is to use a package manager, or our download script, which automatically fetches the latest version of File Browser for your platform.

-### Brew
+=== "Brew"

-```sh
-brew tap filebrowser/tap
-brew install filebrowser
-filebrowser -r /path/to/your/files
-```
+    ```sh
+    brew tap filebrowser/tap
+    brew install filebrowser
+    filebrowser -r /path/to/your/files
+    ```

-### Unix
+=== "Unix"

-```sh
-curl -fsSL https://raw.githubusercontent.com/filebrowser/get/master/get.sh | bash
-filebrowser -r /path/to/your/files
-```
+    ```sh
+    curl -fsSL https://raw.githubusercontent.com/filebrowser/get/master/get.sh | bash
+    filebrowser -r /path/to/your/files
+    ```

-### Windows
+=== "Windows"

-```sh
-iwr -useb https://raw.githubusercontent.com/filebrowser/get/master/get.ps1 | iex
-filebrowser -r /path/to/your/files
-```
+    ```sh
+    iwr -useb https://raw.githubusercontent.com/filebrowser/get/master/get.ps1 | iex
+    filebrowser -r /path/to/your/files
+    ```

-### Configuring
-
-Now your instance is up and running. File Browser will automatically bootstrap a database, in which the configuration and the users are stored. You can find the address in which your instance is running, as well as the randomly generated password for the user `admin`, in the console logs.
-
-Although this is the fastest way to bootstrap an instance, we recommend you to take a look at other possible options, by checking `config init --help` and `config set --help`, to make the installation as safe and customized as it can be.
-
-> [!WARNING]
->
-> The automatically generated password for the user `admin` is only displayed once. If you fail to remember it, you will need to manually delete the database and start File Browser again.
+File Browser is now up and running. Read some [first boot](#first-boot) for more information.

 ## Docker

 File Browser is available as two different Docker images, which can be found on [Docker Hub](https://hub.docker.com/r/filebrowser/filebrowser).

-### Alpine
+=== "Alpine"

-```sh
-docker run \
-  -v /path/to/srv:/srv \
-  -v /path/to/database:/database \
-  -v /path/to/config:/config \
-  -p 8080:80 \
-  filebrowser/filebrowser
-```
+    The 

-The default user has PID 1000 and GID 1000. Please make sure that this user has access to the different mounted volumes. To change the user running inside the Docker image, you need to use the [`--user` flag](https://docs.docker.com/engine/containers/run/#user).
+    ```sh
+    docker run \
+      -v /path/to/srv:/srv \
+      -v /path/to/database:/database \
+      -v /path/to/config:/config \
+      -p 8080:80 \
+      filebrowser/filebrowser
+    ```

-### s6 overlay
+    The default user has PID 1000 and GID 1000. Please make sure that this user has access to the different mounted volumes. To change the user running inside the Docker image, you need to use the [`--user` flag](https://docs.docker.com/engine/containers/run/#user).

-The `s6` image is based on LinuxServer and leverages the [s6-overlay](https://github.com/just-containers/s6-overlay) system for a standard, highly customizable image. It should be used as follows:
+=== "s6 overlay"

-```shell
-docker run \
-  -v /path/to/srv:/srv \
-  -v /path/to/database:/database \
-  -v /path/to/config:/config \
-  -e PUID=$(id -u) \
-  -e PGID=$(id -g) \
-  -p 8080:80 \
-  filebrowser/filebrowser:s6
-```
+    The `s6` image is based on LinuxServer and leverages the [s6-overlay](https://github.com/just-containers/s6-overlay) system for a standard, highly customizable image. It should be used as follows:

-### Notes
+    ```shell
+    docker run \
+      -v /path/to/srv:/srv \
+      -v /path/to/database:/database \
+      -v /path/to/config:/config \
+      -e PUID=$(id -u) \
+      -e PGID=$(id -g) \
+      -p 8080:80 \
+      filebrowser/filebrowser:s6
+    ```

 Where:

@ -79,3 +71,15 @@ Where:
 - `/path/to/database` contains a `filebrowser.db` file

 Both `settings.json` and `filebrowser.db` will automatically be initialized if they don't exist.
+
+File Browser is now up and running. Read some [first boot](#first-boot) for more information.
+
+## First Boot
+
+Your instance is now up and running. File Browser will automatically bootstrap a database, in which the configuration and the users are stored. You can find the address in which your instance is running, as well as the randomly generated password for the user `admin`, in the console logs.
+
+Although this is the fastest way to bootstrap an instance, we recommend you to take a look at other possible options, by checking `config init --help` and `config set --help`, to make the installation as safe and customized as it can be.
+
+> [!WARNING]
+>
+> The automatically generated password for the user `admin` is only displayed once. If you fail to remember it, you will need to manually delete the database and start File Browser again.