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
First, many thanks for this project! I am lookin forward to testing it.
I had some problems getting it to run on Windows and found the source (it was me). Even though it was my fault, I thought a note in the readme could be added for other users:
The backend would not start because linebreaks in worker-start.sh (and other bash-files) were CRLF (Windows), and not LF (Linux). In docker-compose logs this would appear as invalid command \r etc.
I used cookiecutter in Windows with cookiecutter https://github.com/tiangolo/full-stack-fastapi-postgresql, which issued CRLF linebreaks. Once using cookiecutter from WSL bash in Ubuntu, everything worked fine!
I think it generally a good recommendation to use docker-compose, and docker from WSL bash (connected through Windows Docker daemon running on localhost); and set VSCode (if used from Windows), to use LF in global settings with "files.eol": "\n".
The text was updated successfully, but these errors were encountered:
First, many thanks for this project! I am lookin forward to testing it.
I had some problems getting it to run on Windows and found the source (it was me). Even though it was my fault, I thought a note in the readme could be added for other users:
The backend would not start because linebreaks in
worker-start.sh
(and other bash-files) were CRLF (Windows), and not LF (Linux). Indocker-compose logs
this would appear asinvalid command \r
etc.I used cookiecutter in Windows with
cookiecutter https://github.com/tiangolo/full-stack-fastapi-postgresql
, which issued CRLF linebreaks. Once using cookiecutter from WSL bash in Ubuntu, everything worked fine!I think it generally a good recommendation to use docker-compose, and docker from WSL bash (connected through Windows Docker daemon running on localhost); and set VSCode (if used from Windows), to use LF in global settings with
"files.eol": "\n"
.The text was updated successfully, but these errors were encountered: