Web-based file explorer

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • mrblonde wrote:

      This solution is not web-based!
      There is no super friendly, web-based file manager for OMV. Feel free to create one.

      There are plenty of cross platform options. While not super simple, jollyrogr's solution is cross platform. You could connect to shares via webdav. samba works very well and if you have remote users, just have them use vpn.

      Some times, things just aren't easy especially when they are free.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.8
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • jollyrogr wrote:

      I don't see anything on the filerun website about a 3 user limit.
      Have a look here: filerun.com/enterprise

      But they also say: "For family websites with more than three members, contact us and we'll accomodate your usage, at no cost."
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x | Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems in OMV - OMV setup videos - OMV4 Documentation :!:
    • macom wrote:

      namirda wrote:

      it looks like the perfect web-based file manager to me
      How about writing a small [how-to]?
      OK....

      1) As well as the Docker plugin you will need docker-compose because two images are required. Install latest version like this

      Source Code

      1. # curl -L https://github.com/docker/compose/releases/download/1.19.0/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
      2. # chmod +x /usr/local/bin/docker-compose

      Modify the above curl command to make sure you get the latest version.

      2) Check the docker-compose installation

      Source Code

      1. # docker-compose --version
      2. docker-compose version 1.19.0, build 1719ceb

      3) Pull the filerun image

      Source Code

      1. #docker pull afian/filerun

      4) Create a file docker-compose.yml containing the following

      Source Code

      1. version: '2'
      2. services:
      3. db:
      4. restart: unless-stopped
      5. image: mariadb:10.1
      6. environment:
      7. MYSQL_ROOT_PASSWORD: filerun
      8. MYSQL_USER: filerun
      9. MYSQL_PASSWORD: filerun
      10. MYSQL_DATABASE: filerun
      11. volumes:
      12. - /filerun/db:/var/lib/mysql
      13. web:
      14. restart: unless-stopped
      15. depends_on:
      16. - db
      17. links:
      18. - db
      19. image: afian/filerun
      20. ports:
      21. - "81:80"
      22. - "70:70"
      23. expose:
      24. - "81"
      25. volumes:
      26. - /filerun/html:/var/www/html
      27. - /sharedfolders:/user-files
      Display All


      A few things to notice in the yml file above:
      • a) Two containers are required and both have the restart flag set to "unless-stopped" so that filerun will start automatically on boot.
      • b) I have forwarded port 81 from the container so that filerun does not clash with the OMV gui
      • c) Filerun looks for its files in the folder /user-files and so this has been mapped to the omv folder /sharedfolders
      5) Now start filerun

      Source Code

      1. #docker-compose up -d

      6) The first time you run the above yml it will pull mariadb. You should see two new containers appear in the omv docker plugin - one for filrun and the other for mariadb. They should both be 'running'

      7) You can now access filerun by pointing your browser to your-omv-host:81. The default username/password is superuser/superuser.

      Once logged in you should have access to all your omv shared folders - you may need to fiddle about with permissions to achieve this! I have not been successful in using the docker plugin to modify the filerun containers but I haven't really tried too hard. It's just as easy to modify the yml file.

      That's it - good luck

      N

      The post was edited 1 time, last by namirda: Correction ().

    • namirda wrote:

      macom wrote:

      namirda wrote:

      it looks like the perfect web-based file manager to me
      How about writing a small [how-to]?
      OK....
      1) As well as the Docker plugin you will need docker-compose because two images are required. Install latest version like this

      Source Code

      1. # curl -L https://github.com/docker/compose/releases/download/1.19.0/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
      2. # chmod +x /usr/local/bin/docker-compose
      Modify the above curl command to make sure you get the latest version.

      2) Check the docker-compose installation

      Source Code

      1. # docker-compose --version
      2. docker-compose version 1.19.0, build 1719ceb
      3) Pull the filerun image

      Source Code

      1. #docker pull afian/filerun
      4) Create a file docker-compose.yml containing the following

      Source Code

      1. version: '2'
      2. services:
      3. db:
      4. restart: unless-stopped
      5. image: mariadb:10.1
      6. environment:
      7. MYSQL_ROOT_PASSWORD: filerun
      8. MYSQL_USER: filerun
      9. MYSQL_PASSWORD: filerun
      10. MYSQL_DATABASE: filerun
      11. volumes:
      12. - /filerun/db:/var/lib/mysql
      13. web:
      14. restart: unless-stopped
      15. depends_on:
      16. - db
      17. links:
      18. - db
      19. image: afian/filerun
      20. ports:
      21. - "81:80"
      22. - "70:70"
      23. expose:
      24. - "81"
      25. volumes:
      26. - /filerun/html:/var/www/html
      27. - /sharedfolders:/user-files
      Display All

      A few things to notice in the yml file above:
      • a) Two containers are required and both have the restart flag set to "unless-stopped" so that filerun will start automatically on boot.
      • b) I have forwarded port 81 from the container so that filerun does not clash with the OMV gui
      • c) Filerun looks for its files in the folder /user-files and so this has been mapped to the omv folder /sharedfolders
      5) Now start filerun

      Source Code

      1. #docker-compose up -d
      6) The first time you run the above yml it will pull mariadb. You should see two new containers appear in the omv docker plugin - one for filrun and the other for mariadb. They should both be 'running'

      7) You can now access filerun by pointing your browser to your-omv-host:81. The default username/password is superuser/superuser.

      Once logged in you should have access to all your omv shared folders - you may need to fiddle about with permissions to achieve this! I have not been successful in using the docker plugin to modify the filerun containers but I haven't really tried too hard. It's just as easy to modify the yml file.

      That's it - good luck

      N
      Thank you namirda! I was looking for this kind of step-by-step solution for a long time!

      I have also one question about filerun - i would like to use mobile api for it (which requires ssl cert) and also for security reason use it with ssl (to login via "https"). How can i do that? For OMV WebGui i can use a port choosed in WebGui system settings, but how can i secure my plugins (like FileRun or my www apps served by nginx)?

      Thank you in advance,
      Paul
    • namirda wrote:

      Hi Paul - Sorry - can't help you there. It would mean building your own filerun docker image including ssl and I have no idea how to do that!

      SSL must be quite a common requirement though - you might try asking on the filerun site...

      N
      Hmm, i thought that it won't be such issue. I will try to find a solution for that and give some answers in this thread. Thank you again!