We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I read in the CONTRIBUTING.md that Windows development is not currently supported. On top of that, Hosting in Windows is not supported either.
With ridicules minor change to the API code base I managed to Develop and Host the API service on Windows.
NOTE: Frontend works like a charm
Here are the required changes.
Add waitress WSGI poetry add waitress
poetry add waitress
Remove gunicorn specifics from the flagsmith/api/util/logging.py (or add condition to include it or not if running on Linux or Windows).
flagsmith/api/util/logging.py
Update Makefile to include additional action to run with waitress
serve-win: poetry run waitress-serve --host 0.0.0.0 --port 8000 app.wsgi:application
This is it guys - now we can develop and host API in Windows.
None
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
I read in the CONTRIBUTING.md that Windows development is not currently supported. On top of that, Hosting in Windows is not supported either.
With ridicules minor change to the API code base I managed to Develop and Host the API service on Windows.
NOTE: Frontend works like a charm
Describe the solution you'd like.
Here are the required changes.
Add waitress WSGI
poetry add waitress
Remove gunicorn specifics from the
flagsmith/api/util/logging.py
(or add condition to include it or not if running on Linux or Windows).Update Makefile to include additional action to run with waitress
This is it guys - now we can develop and host API in Windows.
Describe alternatives you've considered
None
Additional context
No response
The text was updated successfully, but these errors were encountered: