# Install PHP file manager by including PHP files

> Download the no-Composer ZIP, unpack it and set dirFiles in flmngr.php to run the backend on projects that do not use Composer.

Source: https://n1ed.com/docs/file-manager/php-script  
Original: https://flmngr.com/doc/install-file-manager-server-php-script  
Section: File manager > PHP script (no Composer)  
Every page of n1ed.com has a Markdown copy at its URL + `.md` (`index.md` after a URL that ends in `/`); all of them are in one file: https://n1ed.com/llms-full.txt

## Download

Despite the fact that the best solution for modern projects is to install the [Flmngr Composer package](https://n1ed.com/docs/file-manager/php-composer), there is a set of cases when a project does not use Composer. Especially for those cases, we've prepared a no-Composer version and published it as a ZIP file:

[Download PHP backend](https://flmngr.com/download/flmngr-php.zip)

Unpack it into your project and edit `flmngr.php` file. By default it configured to work with sample files shipped in the archive. Change the value of `dirFiles` parameter to some path where you store your files, for example `/var/www/my-website/files`:

```php
<?php

require __DIR__ . '/vendor/autoload.php';

use EdSDK\FlmngrServer\FlmngrServer;

FlmngrServer::flmngrRequest(
    array(
        'dirFiles' => '/var/www/my-website/files'
    )
);
```

Be sure that this path with files is publicly available through web.

## Update

When you need to update the package, just re-download it and overwrite all the files. If you made some changes to the config inside `flmngr.php`, please copy an existing config to the updated file.

## Link Flmngr with the server

Using the visual Dashboard, you can specify the URLs of your server to link Flmngr with it.

- **File Manager URL** is the full URL of `flmngr.php`.
- **Files URL** is the full URL of `dirFiles` (not a directory path, but an URL).

[Go to Dashboard](https://n1ed.com/dashboard)

![File manager control panel](https://n1ed.com/img/screenshots/docs/widgets/config-editor/file-manager-set-url.png)

> **Note:** Alternatively, you can pass these parameters as [Flmngr.urlFileManager](https://flmngr.com/doc/api-load#method_load__param_urlFileManager) and [Flmngr.urlFiles](https://flmngr.com/doc/api-load#method_load__param_urlFiles) parameters into the Flmngr config. This is useful when you need to use different directories based on the current user to support [multi-user installations](https://n1ed.com/docs/multisite/separating-file-storages).

### Files URL explanation

The **Files URL** option is the prefix Flmngr will add to any file when inserting it into your content (or returning it into a callback of your API call). If you can use Flmngr fine, but all inserted images are broken, please see this sample to understand how it works:

**Files URL** or `Flmngr.urlFiles` client-side parameter

`http://your-website.com/files/`

`/var/www/my-website/files/`

`dirFiles` server-side parameter

\+ `/path/to/image.png`

For example, Flmngr inserts the file `/path/to/image.png` into your content as `http://your-website.com/files/path/to/image.png`, and on the server that file is `/var/www/my-website/files/path/to/image.png`.

## Multi-user environment

Flmngr can work in applications where you have many users with different storages. You can programmatically specify `Flmngr.urlFiles` and `dirFiles` parameters synchronously with values based on the current user's session.

[Multi-user manual](https://n1ed.com/docs/multisite/separating-file-storages)

## S3/Blob support

Flmngr supports not only your own server but also cloud storages: Amazon S3 and Azure Blob. This is an enterprise feature we offer as a separate option.

[S3/Blob support](https://n1ed.com/docs/cloud-storage)
