--- title: File Browser slug: solutions/file-browser docTags: createdAt: 2023-10-09T11:30:34.439Z --- # Overview ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/A623dxdWPGiryE3wah1Fd_function-diagram-solutions-litmusedge-filebrowserdrawio.png) # Provided capabilities The File Browser solution allows litmus edge users to interact with the Litmus Edge core file system to provide additional management capabilities. This does address some customer requests to have more options such as: - be able to manage Litmus flows and its log files more directly - be able to manage files in the FTP directory without the need to use an ftp client or enable the ftp server and make it more usable as a customer drive folder - Be able to manage the space occupied by Litmus Edge update files Currently the File Browser solution provides access to: - FTP Data -> through the folder **ftp-data** At this point, File Browser provides the user with the capability to: - create files and folders - delete files and folder - download files - upload files Further users can: - change the password - change the language # Requirements A Litmus Edge Instance exists. # Running the application using the downloaded Tar File 1. Download the, a tar.gz file from [https://portal.litmus.io/accelerators/litmus-edge-file-browser](https://portal.litmus.io/accelerators/litmus-edge-file-browser) 2. Log in to your Litmus Edge, Navigate to Applications -> Images 3. Click on Upload Image and upload the tar file there 4. Navigate back to Applications -> Containers and enter the following command there: :::BlockQuote docker run -d --restart=unless-stopped -p 41260:8080 --name litmusedge\_filebrowser -v /var/lib/customer/ftp-data/:/data/ftp-data litmus/litmusedge\_filebrowser\:latest ::: After running the command, the container will be running. ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/teMg_uRa_9G1Ir3H83KsL_image.png) The File Browser is now ready and can be accessed through its WebUI. # Logging into the File Browser Open the web browser of your choice and enter into the address bar `:41260` Example: `192.168.2.10:41260` The Login Page opens. ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/VukkPjc_d4W67cQjmNTVB_image.png) The initial Login is: Username: **litmusedge** Password: **litmusedgefilebrowser** **Note:** The user can change the password after the initial login through the Settings. :::hint{type="warning"} The **litmusedge** user is able to: - delete files - create files - Download files The **litmusedge **user is not able to: - Rename or Move directories and files - Execute commands - Share files - Edit files ::: ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/gWg680aNZAG4vKOvTN_Pe_image.png) # (Optional) How to add the File Browser solution to Litmus Edge Manager Marketplace **Note: This is an optional way to deploy the File Browser solution on a Litmus Edge. ** This deployment requires that a Litmus Edge is connected to a deployed Litmus Edge Manager. The user also should have experience in[ adding applications](https://docs.litmus.io/edgemanager/lem-admin-console/product-features/docker-registry) to the LEM Marketplace. The file to be uploaded into the LEM Docker Registry is the tar.gz file *litmusedge\_filebrowser.tar.gz* After uploading the docker image into the LEM Docker registry and setting up the means for authentication, the next step is to prepare the marketplace import. **Step 1:** Download the file *Litmus\_File-Browser\_Marketplace.json* through the *Download* button with the label (LEM Marketplace Listing of File Browser), to import the application to LEM Marketplace. ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/gTfu-s8srDB3jFtzuDdyh_image.png) **Step 2:** Open the JSON file with a editor such as notpad++. **Step 3:** Within the file replace. | \ | The IP or URL of the LEM. | | -------------------- | ------------------------------------------------------ | | \ | The username setup for docker registry authentication. | | \ | The password setup for docker registry authentication. | Examples for replacing these placeholders using notepad++. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/YSwLobQYwirlQoh5_inYf_.blob" size="80" width="573" height="356" position="center" darkWidth="573" darkHeight="356" showCaption="false"} ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/WAN736gkg6tmRceL6QAjO_image.png" size="80" width="894" height="528" position="center" darkWidth="894" darkHeight="528" showCaption="false"} ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/kBEcC82HBLsmDKkarzBGf_image.png" size="80" width="889" height="531" position="center" darkWidth="889" darkHeight="531" showCaption="false"} [The steps below are further explained in the LEM Marketplace Documentation.](https://docs.litmus.io/edgemanager/lem-user-ui/product-features/marketplace-catalogs-and-applications) **Step 4:** Access the LEM User UI via your browser. **Step 5:** Access your company and project and select the Features menu. ​ **Step 6:** Select the Marketplace option.​​ **Step 7:** Select the catalog you want to use.​​ **Step 8:** Select the *Add or Import an Application *icon.​ **Step 9:** Import the downloaded json file. ​ ​**Result:** The application is now part of the catalog. ​​ ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/CY4EWXADl43YyF8UnrMEh_image.png) # (Optional) How to deploy File Browser from Litmus Edge Manager Marketplace **Note: This is an optional way to deploy the Litmus Edge File Browser solution on a Litmus Edge. ** This deployment requires that a Litmus Edge is connected and that the solution has been added to a LEM Marketplace catalog previously. It is expected, that users are knowledgeable about how applications and solutions are [deployed](docId\:bdLsrr7TeEHzdsDFQOyYm) from LEM. Deploying File Browser from LEM has one optional parameters to be provided. ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/UruHB_fx0L3EZ9uKWTjk9_image.png) | **Parameter** | **Description** | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | **PORT** | Used to set the port command -p \:8080.
By default port 41260 will be used but the User is able to change this to another port. |