Sqlite docker-compose file no longer requires .env file

As this is only used for CI this is OK

.github/workflows/docker_test.yaml

@@ -14,6 +14,10 @@ on:
     branches:
       - 'master'
       - 'stable'
+  pull_request:
+    branches:
+      - 'master'
+      - 'stable'
 
 jobs:
 

docker/docker-compose.sqlite.yml

@@ -27,9 +27,9 @@ services:
         volumes:
             # Ensure you specify the location of the 'src' directory at the end of this file
             - src:/home/inventree
-        env_file:
-            # Environment variables required for the dev server are configured in dev-config.env
-            - sqlite-config.env
+        environment:
+            - INVENTREE_DEBUG=True
+            - INVENTREE_DB_ENGINE=sqlite
         restart: unless-stopped
 
     # Background worker process handles long-running or periodic tasks
@@ -44,9 +44,9 @@ services:
         volumes:
             # Ensure you specify the location of the 'src' directory at the end of this file
             - src:/home/inventree
-        env_file:
-            # Environment variables required for the dev server are configured in dev-config.env
-            - sqlite-config.env
+        environment:
+            - INVENTREE_DEBUG=True
+            - INVENTREE_DB_ENGINE=sqlite
         restart: unless-stopped
 
 volumes:

docker/sqlite-config.env

@@ -1,10 +0,0 @@
-# InvenTree environment variables for a development setup
-
-# Set DEBUG to False for a production environment!
-INVENTREE_DEBUG=True
-INVENTREE_DEBUG_LEVEL=INFO
-
-# Database configuration options
-# Note: The example setup is for a PostgreSQL database (change as required)
-INVENTREE_DB_ENGINE=sqlite
-INVENTREE_DB_NAME=/home/inventree/dev/inventree_db.sqlite3