Simple File Manager was created to address a practical need: deploying a lightweight file-management tool inside a Tomcat or WebLogic server. It provides a straightforward way to browse, access, and manage files belonging to an application running on the same application server, especially in environments where no other file-handling interfaces are available.
- Editing configuration files (e.g.,
application.properties,logback.xml) - Reviewing or downloading log files
- Moving or renaming files and directories
- Quickly inspecting generated artifacts or temporary files
Build the docker image with the latest code and run it by issuing the following command:
docker image build -t simple-file-manager . && \
docker container run \
-p 9000:8080 \
--rm \
--name sfm \
-v .:/tmp/myrepo \
simple-file-manager
Then open your browser at http://localhost:9000/sfm.
Note:
-v .:/tmp/myrepomounts the current directory on the host into/tmp/myrepoinside the container.
Simple File Manager can be protected with HTTP Basic Authentication.
- By default, Basic Auth is disabled.
- To enable Basic Auth, you must configure a username and password using either:
- Environment variables
BASIC_AUTH_USERandBASIC_AUTH_PASSWORD, or - JVM system properties
sfm_basic_auth_userandsfm_basic_auth_password.
- Environment variables
- If both environment variables and JVM properties are set, JVM properties take precedence.
- If either the username or password is missing after this resolution, Basic Auth remains disabled.
Example Docker run command enabling Basic Auth via environment variables:
docker container run \
-p 9000:8080 \
--rm \
--name sfm \
-v .:/tmp/myrepo \
-e BASIC_AUTH_USER=myuser \
-e BASIC_AUTH_PASSWORD=mypassword \
simple-file-managerMake sure you have built the Docker image containing the war file you want to get. Then run the following command:
docker container run \
-p 9000:8080 \
--rm \
--name sfm \
-v ./out:/out \
simple-file-manager \
cp /usr/local/tomcat/webapps/sfm.war /outThat will leave the sfm.war file inside the ./out directory, in this folder.
- A Java application server (for example, Apache Tomcat or Oracle WebLogic).
- Obtain the
sfm.warfile (see the section above). - Deploy
sfm.warto your application server as you would with any other web application. - Start or restart the application server so it picks up the new deployment.
If you want to enable HTTP Basic Authentication when running on a Java application server, configure the credentials using either:
- Environment variables
BASIC_AUTH_USERandBASIC_AUTH_PASSWORD, or - JVM system properties
sfm_basic_auth_userandsfm_basic_auth_password.
If both are set, JVM system properties take precedence. If either the username or password is missing after this resolution, Basic Auth remains disabled.
For example, on Tomcat you can export the environment variables in setenv.sh (or the equivalent startup script) before starting the server, or pass the JVM properties:
JAVA_OPTS="${JAVA_OPTS} -Dsfm_basic_auth_user=myuser -Dsfm_basic_auth_password=mypassword"The following application servers have been tested successfully with Simple File Manager:
- Apache Tomcat 10
Simple File Manager was developed by a monkey with a shotgun (me). I am not a developer, and this webapp was built with the help of an AI agent. As a result, nothing in this software should be assumed to follow proper engineering practices, security standards, or production-grade quality.
I take no responsibility for any bad practices, security breaches, vulnerabilities, data loss, unauthorized access, service interruptions, or any other direct or indirect damage resulting from the use, installation, or modification of this tool. Users are solely responsible for evaluating the risks, securing their environment, and determining whether this application is suitable for their needs.
Installation and usage of Simple File Manager are entirely at the user’s own risk. No official support is provided, no updates are guaranteed, and there is no commitment to maintain this project in the future.

