New answers tagged

0

So I believe I came up with a somewhat re-usable solution for this problem using devpi. It allows you to use the same Dockerfile for the testing and production image. Devpi allows me to create my own index which can shadow my production index with versions of software that haven't been officially released. Steps to make this work: 1. Base image from ARG I ...


1

It's a pretty general question, I will try to answer the best I can: If you want to just build and run an image: Build the project: npx expo-cli init react_native_app --npm You need to create a Dockerfile file in your repository Docker build -t {tag_name} . (You can replace '.' eith the Dockerfile path) Docker run... If you want you can create docker ...


1

Your challenges are: Service discovery (usually DNS-based, but there are other approaches) Load balancing for multiple instances of services (server-side with a load balancer, or client-side with smart service discovery) Encryption/TLS Retry and circuit breaker There are few patterns API Gateway routing traffic for API calls not only for external traffic ...


1

The question is: why use a proxy to communicate both applications? What is the point or target (support SSL, security, availability between services? In any case, you need 2 proxies, one in each app, in front of each application, it is the best way to use it. You can also use tunnels, like SSH tunnel or Stunnel that support TLS


0

We shouldn't need to create image on each stage and should promote the same image tag in across environments ( i.e whatever we have in UAT will get QA/TESTED and released to PROD as artifact ), how are you managing this image promotion across environment ? what are other release process look like ? Yes, rebuilding images is considered an anti-pattern in ...


0

Although difficult to give a canonical answer, I think I understand your frustration. My opinion is that you are focussing on promoting the wrong thing - the image. I would start with the concept of "Dev-Prod parity" (or in your case, UAT/Prod parity). This concept says: Keep development, staging, and production as similar as possible The ...


Top 50 recent answers are included