Skip to content

Separate nginx image is annoying #74

@agoncharov-reef

Description

@agoncharov-reef

I don't like having nginx outside of project repo. I think it's a bad idea:

  1. 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
  2. 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'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions