The inclusion of PATH as an environment variable causes the app to fail to launch, I understand that this is included in the compose file on framagit so maybe this is an upstream issue. Either way, removing that one line allows the app to launch and I've had no issues.
O2025-04-16T01:29:10.623068329Z /usr/bin/env: 'node': No such file or directory
O2025-04-16T01:29:04.828829113Z /usr/bin/env: 'node': No such file or directory
O2025-04-16T01:29:16.371219347Z /usr/bin/env: 'node': No such file or directory
O2025-04-16T01:28:58.052605557Z /usr/bin/env: 'node': No such file or directory
The inclusion of PATH as an environment variable causes the app to fail to launch, I understand that this is included in the compose file on framagit so maybe this is an upstream issue. Either way, removing that one line allows the app to launch and I've had no issues.
```
O2025-04-16T01:29:10.623068329Z /usr/bin/env: 'node': No such file or directory
O2025-04-16T01:29:04.828829113Z /usr/bin/env: 'node': No such file or directory
O2025-04-16T01:29:16.371219347Z /usr/bin/env: 'node': No such file or directory
O2025-04-16T01:28:58.052605557Z /usr/bin/env: 'node': No such file or directory
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The inclusion of PATH as an environment variable causes the app to fail to launch, I understand that this is included in the compose file on framagit so maybe this is an upstream issue. Either way, removing that one line allows the app to launch and I've had no issues.
Oh, that's weird, I wasn't seeing that at all?
OK, but let's get rid of it then if you're seeing the fix work / no difference.
Thanks!
I'm not sure exactly what the issue is but I've only ever seen that exact output on new gancio deployments.