A common security recommendation for web applications is to store database files outside the web document root whenever possible.
For this reason, some users may wonder why SQLiteManager stores its management database within the application directory.
SQLiteManager intentionally keeps its management database within the application directory.
SQLiteManager is intended as an administrative tool and includes advanced functionality such as user-defined PHP code execution through the UDF mechanism.
Because administrator-defined PHP code can be executed by the application, the primary security boundary is not the database file itself, but access to the SQLiteManager installation as a whole.
Protecting only the database file would provide limited practical security benefits if access to the application itself were already compromised.
For this reason, the project focuses on securing the entire SQLiteManager installation directory rather than treating the management database as a separate security boundary.
Administrators are strongly encouraged to restrict access to the entire SQLiteManager directory using one or more of the following methods:
SQLiteManager assumes that all authenticated users are trusted administrators with full authority over the databases and functionality managed by the application. The project is not intended to provide internal privilege separation, delegated user accounts, or role-based access control.
Keeping the management database within the application directory simplifies installation, upgrades, migration, and compatibility with a wide range of hosting environments.
While storing the database outside the document root is a valid approach for many web applications, SQLiteManager prioritizes whole-application protection and operational simplicity.