Litmus Edge File Browser

overview provided capabilities the litmus edge 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 litmus edge file browser solution provides access to ftp data > through the folder ftp data litmus flows files > through the folder flows at this point, litmus edge file browser provides the user with the capability to create files and folders delete files and folder download files upload files further can users change the password change the language requirements a litmus edge instance exists running the application using the downloaded tar file after checkout, a tar gz file is expected to be downloaded log in to your litmus edge, navigate to applications > images click on upload image and upload the tar file there navigate back to applications > containers and enter the following command there docker run d restart=unless stopped p 41260 8080 name litmusedge filebrowser v /var/lib/customer/ftp data/ /data/ftp data v /var/lib/loopedge flows ui/flows/ /data/flows litmus/litmusedge filebrowser\ latest after running the command, the container will be running the litmus edge file browser is now ready and can be accessed through its webui logging into the litmus edge file browser open the web browser of your choice and enter into the address bar \<ip of your litmus edge> 41260 example 192 168 2 10 41260 the login page opens the initial login is username litmusedge password litmusedgefilebrowser note the user can change the password after the initial login through the settings (optional) how to add the litmus edge file browser solution to 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 to a deployed litmus edge manager the user also should have experience in adding applications 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 edge file browser marketplace json through the download button with the label (lem marketplace listing of litmus edge file browser), to import the application to lem marketplace step 2 open the json file with a editor such as notpad++ step 3 within the file replace true false 194false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type examples for replacing these placeholders using notepad++ 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 ​ ​ step 10 the application is now part of the catalog ​​ (optional) how to deploy litmus edge 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 from lem deploying litmus edge file browser from lem has one optional parameters to be provided true falsefalse unhandled content type false unhandled content type false unhandled content type false unhandled content type