Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert Caddy to deploy frontend and backend as one container #219

Open
1 task
fergmac opened this issue Nov 27, 2024 · 2 comments
Open
1 task

Revert Caddy to deploy frontend and backend as one container #219

fergmac opened this issue Nov 27, 2024 · 2 comments
Assignees
Labels

Comments

@fergmac
Copy link
Collaborator

fergmac commented Nov 27, 2024

Describe the task
Currently unable to get the Caddy reverse proxy to forward to maps.gov.bc for retrieving map tile vector data

Purpose
To revert away from Caddy to host frontend static files with Django whitenoise tool

Acceptance Criteria

  • Backend service deploys and application is accessible at URL

Additional context

  • Add any other context about the task here.
  • Or here
@fergmac fergmac added the ready label Nov 27, 2024
@fergmac fergmac self-assigned this Nov 27, 2024
@fergmac fergmac changed the title Resolve Caddy related Mapbox issues Revert Caddy to deploy frontend and backend as one container Dec 10, 2024
@fergmac
Copy link
Collaborator Author

fergmac commented Jan 8, 2025

I have done the following while debugging the failing backend container:

  • Audited the secrets and environment variables
  • The database OpenShift service object is referenced as an environment variable in the backend container
  • Checked network policies exist and are allowing same namespace traffic
  • The database container is deploy successfully and accepting traffic
  • I can log into the database using the dev database secrets
  • Refactored the django database configuration to simply debugging

@fergmac
Copy link
Collaborator Author

fergmac commented Jan 9, 2025

Initial problem ended up being the network policy. Although it was setup and present you can add the specific license plate number to the network policy to be more specific. This was not required in other nr-* repos referenced during pipeline work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants