You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found this issue while trying to recreate another issue. It was on a new clone in master and in a fresh virtual env - so I went through the steps of installation. See if anybody can reproduce or can suggest a solution.
Tip: There are .env or .flaskenv files present. Do "pip install python-dotenv" to use them.
cs-minibot-platform@1.0.0 webpack
webpack
Webpack is watching the files…
Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
Debug mode: off
Usage: flask run [OPTIONS]
Error: Could not locate a Flask application. You did not provide the "FLASK_APP" environment variable, and a "wsgi.py" or "app.py" module was not found in the current directory.
The text was updated successfully, but these errors were encountered:
I was able to replicate this bug by unstalling the python-dotenvpackage from my (working) virtual environment. Try this:
pip install python-dotenv
You did say it was a clean install from master though (and python-dotenv is in requirements.txt), so this might not be the solution you're looking for.
I found this issue while trying to recreate another issue. It was on a new clone in master and in a fresh virtual env - so I went through the steps of installation. See if anybody can reproduce or can suggest a solution.
================= MINIBOT CLIENT GUI =================
=========== STARTING BASESTATION ===============
Webpack is watching the files…
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
Usage: flask run [OPTIONS]
Error: Could not locate a Flask application. You did not provide the "FLASK_APP" environment variable, and a "wsgi.py" or "app.py" module was not found in the current directory.
The text was updated successfully, but these errors were encountered: