Introduce "dev environment" and dotenv

There are now two dockerfiles. One for production, one for development.
All configuration is now also handled through dotenv files,
which these dotenv files, as well as the included VSCode launch tasks
use.
This commit is contained in:
2023-03-28 00:54:04 +02:00
parent 831166f38b
commit b8220732ee
7 changed files with 112 additions and 93 deletions

5
.vscode/launch.json vendored
View File

@ -15,8 +15,8 @@
"FLASK_APP": "backend/app.py",
"FLASK_ENV": "development",
"FLASK_DEBUG": "1",
"DBSTRING": "mysql://devuser:devpw@127.0.0.1:3306/karaoqueue"
},
"envFile": "${workspaceFolder}/.env.dev",
"args": [
"run",
"--no-debugger",
@ -36,6 +36,7 @@
"FLASK_ENV": "development",
"FLASK_DEBUG": "1"
},
"envFile": "${workspaceFolder}/.env.dev",
"args": [
"run",
"--no-debugger"
@ -54,6 +55,7 @@
"FLASK_ENV": "development",
"FLASK_DEBUG": "1"
},
"envFile": "${workspaceFolder}/.env.dev",
"args": [
"run",
"--no-debugger",
@ -73,6 +75,7 @@
"FLASK_ENV": "development",
"FLASK_DEBUG": "1"
},
"envFile": "${workspaceFolder}/.env.dev",
"args": [
"run",
"--no-debugger",