If you can use a static IP then just use that, it’ll startup and just return 503‘s if it doesn’t respond. Use the resolver directive to point to something that can resolve the host, regardless if it’s currently up or not. Resolve it at the location level, if you can’t do the above (this will … Read more
I do not think Nginx can be used for what you’re trying to use it for. While it can be used to proxy tcp streams or load balance them, it’s not necessarily knowledgable of the protocol and request structure within them. So to answer your question: from database sharding perspective – is it possible to … Read more
You can use server-snippet annotation. This seems like exactly what you want to achieve.
Reference: http://wiki.nginx.org/HttpRewriteModule#rewrite If the replacement string begins with http:// then the client will be redirected, and any further >rewrite directives are terminated. So remove the http:// part and it should work: location ~ /[0-9]+ { rewrite “/([0-9]+)” /v.php?id=$1 break; }
Your ingress definition creates rules that proxy traffic from the {path} to the {backend.serviceName}{path}. In your case, I believe the reason it’s not working is that /app is proxied to app-service:80/app but you’re intending on serving traffic at the / root. Try adding this annotation to your ingress resource: nginx.ingress.kubernetes.io/rewrite-target: / Source: https://github.com/kubernetes/ingress-nginx/tree/master/docs/examples/rewrite
Celery and RQ is overengineering for simple task. Take a look at this docs – https://docs.python.org/3/library/concurrent.futures.html Also check example, how to run long-running jobs in background for Flask app – https://stackoverflow.com/a/39008301/5569578
This may get closed as opinion based, but for what it’s worth my opinion is that docker should be involved in networking up to the transport layer (TCP/UDP) but no higher (HTTP). Thus I would say no you should not install nginx as a reverse proxy directly on your docker host directly and yes you … Read more
You’re right, you need to use NGINX’s stream module by adding a stream section to your .conf file: stream { server { listen <your incoming Mongo TCP port>; proxy_connect_timeout 1s; proxy_timeout 3s; proxy_pass stream_mongo_backend; } upstream stream_mongo_backend { server <localhost:your local Mongo TCP port>; } }
The W3 spec on Access-Control-Allow-Origin explains that multiple origins can be specified by a space-separated list. In practice, though, this is unlikely to be interpreted correctly by current implementations in browsers (eg fails for Firefox 45 at time of writing); summed up by this comment. To implement what you need, then the following nginx snippet … Read more