ssl-proxy | Simple zero-config SSL reverse proxy | TLS library

• If you use Chromium-based browser, then http://___hashhere___.ipfs.localhost:8080/ will have window.isSecureContext set to true and you will have access to all Web APIs. No need for TLS setup for dev on localhost with Chromium (Firefox has a bug).

• If you are running IPFS Companion, you may want to disable it when you develop your app, to ensure requests for IPFS resources are not redirected to the gateway set in browser extension's Preferences.

• In production, you deploy go-ipfs behind a reverse proxy and that proxy terminates TLS. You can control the protocol scheme and host used in some of redirects via X-Forwarded-Proto and X-Forwarded-Host headers, as noted in go-ipfs/docs/config.md

Looks like you are missing 👀 the entrypoint websecure annotation so that Traefik also works on port 443

D'oh! Looks like RemoteImage is the answer: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/docker/#RemoteImage

EDIT:

I tried

Varnish is a transparent HTTP proxy. It will forward to backend whatever Host header was sent to it by the client (your browser). So if you have accessed it via http://localhost/, then localhost is what your backend will see in the Host header.

Additionally, you should mostly never use DNS names in Varnish backend definitions. It should look like this instead:

When a Docker container is run, it runs the ENTRYPOINT (only), passing the CMD as command-line parameters, and when the ENTRYPOINT completes the container exits. In the Dockerfile the ENTRYPOINT has to be JSON-array syntax for it to be able to see the CMD arguments, and the script itself needs to actually run the CMD, typically with a line like exec "$@".

The single simplest thing you can do to clean this up is not to try to go back and forth between environment variables and positional parameters. The ENTRYPOINT script will be able to directly read the ENV variables you set in the Dockerfile (or override with docker run -e options). So if you delete the first lines of the script that set these variables from positional parameters, and make sure to run the CMD

You have a few options. The warnings from Kompose are because it doesn't currently support storing data on the host so you could look to address that. You could use emptyDir as a way of doing temporary storage or look at configuring hostPath but it depends what your target environment is. If you are looking to deploy to a cloud provider then you'd be best to look at options for their supported storage.

Another option would be to create a helm chart that uses the official helm chart for postgres and maybe also for nginx, if you don't decide to switch to nginx-ingress. This could make sense if you're looking to use kubernetes for the long-term and want a deployment descriptor that takes advantage of kubernetes features and can be deployed on different types of kubernetes cluster.

If you are just looking to have a quick way to run things on a single machine then, as @johnharris85 points out, Compose on Kubernetes would make a lot of sense for you.

You have to set the capabilities and force it to use a manual proxy. Username and password are optional. PROXY should be in the form of 'http://68.251.250.193:8080'

Correct structure