I’m just setting up a simple Django in fly.io to kick the tyres =).
fly launch to automatically create the configuration files (e.g.
One issue is that my Django app itself is in a subdirectory.
So it seems when I do
fly deploy, the Gunicorn process is confused by the paths.
As a quick hack, I tried editing the Dockerfile to change
CMD ["gunicorn", "--bind", ":8000", "--workers", "2", "foobar.foobar.wsgi"]
It got a bit further along, then errored out on trying to find
Is there some easier way to tell fly.io how to handle the above directory structure, where the Django app isn’t directly in the root?