Reloading inside symlinked working dir

[quard8]

We're using Capistrano for deployment. One of Capistrano's features is a symlinked working directory. For example here is dir structure:

/app/current/ - current version symlinked from /app/released/1234
/app/released/1234 - current version
/app/released/5678 - old version

With reload feature, we can reload granian, but it will look into not current version, but old version (where it was initially started).

Is there way to always use /app/current/ on reload?

[gi0baro]

@quard8 I won't use the reloader in production.
I'd rather emit a SIGHUP to the granian main process after you change the symlink target.

[quard8]

One of the issues might be supervisord and where granian was started.

[program:granian]
user = deploy
command=/home/deploy/.local/bin/uv run granian --interface wsgi app.wsgi:application --backpressure 50 --log-level info --log --pid-file /app/current/tmp/pids/granian.pid
directory=/app/current/

[gi0baro]

Yeah, I think you should stay out of the current folder. I'd try smth like this instead:

[program:granian]
user = deploy
command=/home/deploy/.local/bin/uv run granian --interface wsgi current.app.wsgi:application --backpressure 50 --log-level info --log --pid-file /app/run/pids/granian.pid
directory=/app

disclaimer: I'm definitely not a supervisord expert.

[quard8]

In this case we can't use uv correctly, because env is incorrect.

Are there plans to add a working-dir option? :)

[gi0baro]

In this case we can't use uv correctly, because env is incorrect.

You can change the command to point directly to the granian binary inside the env.

Are there plans to add a working-dir option? :)

No, but you can open a feature request for that :)
I'm not sure it would solve your issue though: Granian relies on the Python import system to load your app. So it's a bit unclear to me if the python path and all that would be correct if we start tampering with the import system.

[quard8]

Posted a feature request here #583