![]() To be more specific, all of the files in env/bin had the shebang #!/codebuild/output/src715682316/src/env/bin/python, so of course running env/bin/gunicorn on the production server would fail. In my case, the machine installing the packages and actually running the packages was different. ![]() It was just Python scripts with a shebang of the path to the Python interpreter on the build machine. contained actual binaries of native libraries but that was not the case. I was using AWS CodeBuild to build the virtual environment and run tests and using CodeDeploy to put the built artifacts onto the production server and launch the new version (all environments were Ubuntu 20.04). For future readers, I had this issue when trying to launch a Django server using gunicorn.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |