Logs polluted with 'buildpack=nginx at=app-initialization' despite existance of /tmp/app-initialized

ryandotsmith / nginx-buildpack

Run NGINX in front of your app server on Heroku

457 stars 248 forks source link

Logs polluted with 'buildpack=nginx at=app-initialization' despite existance of /tmp/app-initialized #80

Closed olegbaslak closed 5 years ago

olegbaslak commented 5 years ago

However, application (.netcore2.2) actually can be reached through ngnix.

Specifying other file in $HOME directory with -f params didn't give any result

yangningBU commented 3 years ago

I'm experiencing the same thing. Besides polluting the logs, is it harmful at all? It makes me feel nginx isn't up completely even though it's serving my application correctly as well as proxying to a secondary site