filesysorg/jfileserver-enterprise repository overview

JFileServer Enterprise java file server provides support for SMB/CIFS (including SMB2 and SMB3), FTP/FTPS and NFS file server protocols with support for virtual filesystems and database filesystems.

To run the JFileServer Enterprise server with SMB and/or SMB3 enabled requires a licence key, request a trial licence by emailing [email protected]⁠.

This image uses the Java NIO filesystem driver to map a shared drive to a local folder which can be accessed using an SMB/CIFS client, by mapping a network drive from the client.

The default share name is 'jfileshare' with a default user of 'jfilesrv' using password 'java'.

The JFileServer SMB server is configured to use the standard ports for the SMB server (445, 137-139). On linux, Mac, unix systems you can map the SMB file server to the host so it will be accessible remotely, using the command :-

docker run filesysorg/jfileserver-enterprise -p 445:445

The JFileServer Enterprise file server can also be started using a docker-compose.yml file, here is a sample docker-compose file, just replace the 'MAP-TO-A-LOCAL-FOLDER' entries with your local paths :-

services:
  jfileserver:
    image: filesysorg/jfileserver-enterprise:1.2.16
    environment:
      JFSRV_SMBDIALECTS: "SMB2,SMB3"
      JFSRV_FTP_ENABLE: "true"
      JFSRV_FTP_PORT: 1121
    ports:
      - "445:445"
      - "8080:8080"
      - "21:1121"
      - "8000:8000"
    volumes:
      - <MAP-TO-A-LOCAL-FOLDER>:/jfileserver/fileShare
      - <MAP-TO-A-LOCAL-FOLDER>:/jfileserver/licence
    depends_on:
      - jfileserver-postgres

  jfileserver-postgres:
    image: postgres:9.6
    environment:
      POSTGRES_DB: jfileserver
      POSTGRES_USER: jfileserver
      POSTGRES_PASSWORD: fileserver
    command: postgres -c max_connections=300 -c log_min_messages=LOG
    ports:
      - "5432:5432"
    volumes:
      - jfileserver-db-volume:/var/lib/postgresql/data

volumes:
  jfileserver-data-volume:
    external: true
  jfileserver-db-volume:
    external: true

On Windows you will need to setup a network route to the JFileServer container :-

1. Get the Docker VM IP address using 'docker-machine ip default'
2. Start the JFileServer container without a port mapping using 'docker run filesysorg/jfileserver'
3. Get the IP address of the JFileServer container using 'docker inspect | findstr IPAddress'
4. Add network routing to the JFileServer container 'route add /P MASK 255.0.0.0 . For example if the container IP address is 172.17.0.2 and the Docker machine IP is 192.168.99.100 the routing command would be 'route add /P 172.0.0.0 MASK 255.0.0.0 192.168.99.100'
5. Map a network drive from the Windows host using a UNC path of '\\jfileshare' using user 'jfilesrv' with password 'java'.

The configuration and various paths can be mapped to host paths using the -v command line switch. The default paths are :-

Configuration file - /jfileserver/fileSrvConfig.xml

Default local shared folder - /jfileserver/fileShare/

Logs folder - /jfileserver/logs/

Licence folder - /jfileserver/licence/

To redirect the default shared folder to a host folder you would use '-v <local_path>:/jfileserver/fileShare/'. To redirect the log file to a host folder you would use '-v <local_path>:/jfileserver/logs', the default log file name is 'jfileserver.log'.

On Windows the default Docker setup only allows host paths within the \Users folder so to redirect the logs folder to a host path you would use '-v "/c/Users//logs:/jfileserver/logs"'. The log file 'jfileserver.log' should appear within the hosts logs\ folder as the JFileServer starts up.

For more information and the latest news about JFileServer see http://www.filesys.org⁠. More documentation is available on the FileSys.Org Wiki at http://www.filesys.org/wiki/⁠.