Extract nginx away from console container

[ygrishajev]

Current Issue:
Currently, Nginx and SSL are configured within the same image that's running the application container. This setup mixes application logic with infrastructure concerns, leading to several issues:

• Separation of Concerns: The current configuration mixes application logic with infrastructure (reverse proxy and SSL), which should be handled separately.
• Environment Differences: The local environment doesn't require a reverse proxy, while the remote environment does. This discrepancy leads to code duplication and complicates maintenance.
• Maintainability: Combining these concerns into a single container creates confusion and makes it harder to maintain the setup.
• Security: Harder to implement unprivileged access for the application/proxy

Proposed Solution:
To address these issues, we should separate the Nginx and SSL configuration into a sidecar container. This is a common pattern that helps isolate infrastructure concerns from application logic.

Benefits:

• Clear Separation: By using a sidecar container, the application logic and infrastructure concerns are clearly separated.
• Consistency Across Environments: This setup allows for a consistent configuration between local and remote environments, reducing code duplication and maintenance complexity.
• Simplified Maintenance: Maintaining and updating the reverse proxy and SSL configurations become easier when they are isolated from the application container.

Implementation Guide:
There is a comprehensive guide on how to implement an Nginx sidecar on Google Cloud Platform (GCP). This guide can be adapted to our needs to set up the sidecar container effectively.
Implementing Nginx Sidecar on GCP