You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't like having nginx outside of project repo. I think it's a bad idea:
The reason to have it outside of project is that we can update it in cookiecutter and thus update it on every project automatically, but we can update it via cruft update as well but manually, thus having more control over the process
It is rather ANNOYING that I don't have control over the nginx image, for example i've been hit twice already with letsencrypt configuration: there are cases when I want to intervent letsencrypt validation process and I cannot do that because
nginx:
image: 'ghcr.io/reef-technologies/nginx-rt:v1.0.0'
The text was updated successfully, but these errors were encountered:
I don't like having nginx outside of project repo. I think it's a bad idea:
nginx:
image: 'ghcr.io/reef-technologies/nginx-rt:v1.0.0'
The text was updated successfully, but these errors were encountered: