Zicklag zicklag

Creating a Proxy Proxy for Skipping Proxy Authentication Prompts

Update

I found an easier way to do this with a Go program that doesn't require writing a script and installing node. Check out this comment.

Original Solution

Some programs support a proxy, but they don't support authentication without prompting. This is the case with Chrome and VSCode. This caused me problems particularly when trying to automate Chrome with Selenium. The workaround is to run a local proxy, set your http_proxy environment variables to the local proxy, and tell the local proxy to, in turn, proxy requests to your real proxy and to include your username and password.

	version: '3.5'

	# WARNING: Haven't tested this version of this YAML exactly, but it should be correct.

	services:
	master-1:
	image: chrislusf/seaweedfs:latest
	networks:
	- hostnet
	command: "master -port=9333 -defaultReplication=001 -peers=localhost:9333,localhost:9334,localhost:9335"

	version: '3.5'
	services:
	mfsmaster-1:
	image: lizardfs-test:latest
	command: master ha master
	networks:
	- hostnet
	environment:
	DEBUG: "true"
	MFSMASTER_PERSONALITY: ha-cluster-managed

	version: '3.5'

	services:
	taiga:
	image: quay.io/riotkit/taiga:4.2.7
	networks:
	- default
	- webgateway
	volumes:
	- media:/usr/src/taiga-back/media

	cloudinit-userdata: \|
	ca-certs:
	trusted:
	- \|
	-----BEGIN CERTIFICATE-----
	..........certcontents.....
	-----END CERTIFICATE-----

	//! Docker related types

	use anyhow::format_err;

	use std::str::FromStr;
	use std::fmt;

	/// The definition of a Docker container run and all of its attributes such as image, volumes, etc.
	#[derive(Default, Debug)]
	pub(crate) struct ContainerSpec {

	//! run this example with
	//! cargo run --example scrollable
	//!
	use crossterm::{
	cursor::Hide,
	cursor::Show,
	event::{
	self,
	Event,
	KeyEvent,

	while sleep ${@:-1};
	do vmstat --unit M \| awk '/[0-9].*/ { printf "Free Memory: %sM CPU Usage: %s%s\n" , $4, $13, "%" }';
	done


	//
	// Logging macros
	//
	// These act similar to the `log` crate's macro , but it uses our simpler and ( intentionally )
	// synchronous logging implementation.
	//

	// Log a message with the given level
	macro_rules! log {